This is the mail archive of the
mailing list for the binutils project.
RE: Broadcom XLP support
> -----Original Message-----
> From: Paul_Koning@Dell.com [mailto:Paul_Koning@Dell.com]
> Sent: Wednesday, August 03, 2016 8:13 PM
> To: email@example.com
> Cc: ANDY KENNEDY; firstname.lastname@example.org
> Subject: Re: Broadcom XLP support
> > On Aug 3, 2016, at 6:01 PM, Maciej W. Rozycki <email@example.com> wrote:
> > ...
> >> Otherwise, there are missing entries in various files in binutils -- missing
> >> from what the XLR has in it. Since these are closely related, I should be
> >> able to figure out what to put where for the XLP in those missing locations.
> >> Doing that, nearly from scratch (using Khem Raj's patch), should grant me the
> >> copyright for the code, though IANAL...
> > That might be questionable, I advise enquiring with FSF. It might be
> > easier if XLP instruction set documentation was available, but it's NDA'd
> > I believe. Granted, with that in hand and using XLR as a template it
> > would be hard to come up with code substantially different from any
> > previously proposed.
> Then again, Broadcom (or its predecessors) distributed their modified GPL-licensed tool chains,
> never to my knowledge claiming that the GPL didn't apply to those modified versions.
That's what I thought too. I mean, you added to and DISTRIBUTED binary
code that is CLEARLY a derived work -- even, an original work of the
FSF. So, to that end, I believe that you forfeit the rights of the IP
base upon that action.
Again, IANAL, however, $0.02.