public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Inclusion of GPLv3 code
Date: Tue, 21 Sep 2010 03:51:12 -0400	[thread overview]
Message-ID: <201009210351.16288.vapier@gentoo.org> (raw)
In-Reply-To: <20100921073337.90A39157D71@gemini.denx.de>

On Tuesday, September 21, 2010 03:33:37 Wolfgang Denk wrote:
> Graeme Russ wrote:
> > I know you are favouring a migration of U-Boot to GPLv3, but currently it
> > is still licensed under v2 (although most code is v2 'or later')
> > 
> > I have some v3 code I would like to bring in (from GRUB). Will that cause
> > any issues?
> 
> It is my understanding that you cannot "downgrade" GPLv3 code, i. e.
> you cannot link it into a GPLv2 project.  But then, I'm not a license
> expert, and IANAL.

in-my-not-a-lawyer-opinion, i think introducing GPLv3 code makes the final 
output GPLv3 only if the build includes it.

so if the imported GRUB code stays at GPLv3, and is only for x86, and all of 
the code Graeme is using from u-boot is GPLv2+, then the final result there is 
under GPLv3 only.  but all his GPLv3 code, assuming it's specific to x86, wont 
affect other architectures.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100921/63145fec/attachment.pgp 

  reply	other threads:[~2010-09-21  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 12:06 [U-Boot] Inclusion of GPLv3 code Graeme Russ
2010-09-21  7:33 ` Wolfgang Denk
2010-09-21  7:51   ` Mike Frysinger [this message]
2010-09-21  8:37     ` Wolfgang Denk
2010-09-21  8:43       ` Mike Frysinger
2010-09-21  9:29         ` Graeme Russ
2010-09-21  9:36         ` Graeme Russ

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=201009210351.16288.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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