From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [EXT] Re: Cavium/Marvell Octeon Support
Date: Tue, 5 Nov 2019 09:16:56 -0500 [thread overview]
Message-ID: <20191105141656.GD4181@bill-the-cat> (raw)
In-Reply-To: <20191105083335.7D78A24009F@gemini.denx.de>
On Tue, Nov 05, 2019 at 09:33:35AM +0100, Wolfgang Denk wrote:
> Dear Aaron,
>
> In message <5376617.97hUrJXovB@flash> you wrote:
> >
> > > Again you don't answer my question. Why do you need a special new
> > > API for such code? Why do you not just link that code with the rest
> > > of U-Boot?
> >
> > The code in question that is calling the API is not GPL and hence cannot be
> > linked with U-Boot though the phy code is GPL.
>
> Ouch. I was afraid to hear that.
>
> Please be aware that your newly created API does NOT implement a GPL
> license exception. the only interface that allows for non-GPL code
> to be run under control of U-Boot is the standalone program
> interface, which is intentionally very restricted.
>
> In other words: what you are doing here is a clear (and intentional,
> which makes it even worse) GPL license violation.
>
> > > It has been mentioned before, but just to be sure: this code which
> > > uses your new API is licensed under a GPLv2 conforming lincense?
> > >
> > There should be no need. None of the code is linked against U-Boot, either at
> > compile time nor at runtime. The application doesn't even know where it is
> > located except by looking for a named block of memory.
>
> It does not have to be linked. You access internal interfaces of
> U-Boot that have not been exported for non-GPL use, so your code
> still has to be licensed under GPLv2 or a compatible license.
I'm just following up to say that I agree with Wolfgang here.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191105/3adab658/attachment.sig>
next prev parent reply other threads:[~2019-11-05 14:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 3:50 [U-Boot] Cavium/Marvell Octeon Support Aaron Williams
2019-10-24 6:44 ` Chris Packham
2019-10-25 15:13 ` Daniel Schwierzeck
2019-10-26 22:15 ` Tom Rini
2019-10-27 3:08 ` [U-Boot] [EXT] " Aaron Williams
2019-10-27 2:34 ` Aaron Williams
2019-10-29 13:12 ` Wolfgang Denk
2019-10-30 16:20 ` Daniel Schwierzeck
2019-10-30 17:21 ` Wolfgang Denk
2019-10-30 21:23 ` Aaron Williams
2019-10-31 10:36 ` Wolfgang Denk
2019-10-31 17:59 ` Aaron Williams
2019-11-04 15:44 ` Wolfgang Denk
2019-11-04 16:23 ` Tom Rini
2019-11-05 2:08 ` Aaron Williams
2019-11-05 8:37 ` Wolfgang Denk
2019-11-05 10:22 ` Aaron Williams
2019-11-05 11:36 ` Wolfgang Denk
2019-11-05 23:09 ` Aaron Williams
2019-11-06 15:06 ` Wolfgang Denk
2019-11-06 22:18 ` Aaron Williams
2019-11-07 0:21 ` Tom Rini
2019-11-05 14:15 ` Tom Rini
2019-11-05 1:57 ` Aaron Williams
2019-11-05 8:33 ` Wolfgang Denk
2019-11-05 14:16 ` Tom Rini [this message]
2019-10-30 22:05 ` [U-Boot] " Tom Rini
2019-10-30 23:36 ` [U-Boot] [EXT] " Aaron Williams
2019-10-31 10:40 ` Wolfgang Denk
2019-10-31 18:01 ` Aaron Williams
2019-11-04 17:22 ` Tom Rini
2019-11-05 2:13 ` Aaron Williams
2019-11-05 14:09 ` Tom Rini
2019-10-31 13:26 ` Tom Rini
2019-10-31 18:04 ` Aaron Williams
-- strict thread matches above, loose matches on Subject: below --
2019-11-06 0:03 Aaron Williams
2019-11-07 0:34 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191105141656.GD4181@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox