public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vincent Launchbury <vincent@doublecreations.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Non-free software in Gentoo
Date: Tue, 29 Dec 2009 21:42:06 -0500	[thread overview]
Message-ID: <4B3ABDFE.9050209@doublecreations.com> (raw)
In-Reply-To: <20091230005035.GA21380@kroah.com>

Greg KH wrote:
> The fact that some people claim that the firmware blobs somehow violate
> the GPLv2 license of the kernel is a claim, not a fact, so please do not
> state it as such.  

Hi Greg,

Thanks for your reply.

I think you misunderstood my point though. I wasn't saying that the
firmware violates the GPL, I have no idea whether it does or not. I was
saying that some of the firmware is non-free software, and therefore the
license should include more than just GPL-2. This especially effects
people using ACCEPT_LICENSE to maintain a free system.

> Also note that the majority of these firmware blobs are now removed
> from the kernel, and are in a separate patckage, so this might be
> totally irrelevant at this point in time.

This may be true, but the packages in the main tree still contain
non-free firmware. If this is fixed in a later release, then GPL-2 would
be fine for those.

> So please don't state that the Linux kernel is not properly listed as
> the GPLv2, because it is.

In linux-2.6.31 for example, here are some excerpts from
firmware/WHENCE:

Regarding the keyspan USB driver:
	This firmware may not be modified and may only be used with
	Keyspan hardware.

and the emi26 driver:
	This firmware may not be modified and may only be used with the
	Emagic EMI 2|6 Audio Interface.

I'm not sure if this git repo is part of a separate package or not, but
it seems the same terms are present:
http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=blob;f=WHENCE;h=83d245bee1ec44cbd5c0e1a53a3989c57f675c91;hb=f20b0674534a444ae74239843cac19f72c64912b

Which is why I think the license should be amended. If I'm mistaken,
please do correct me, but based on my above notes, I believe it should
be updated.

Thanks,
Vincent.



  reply	other threads:[~2009-12-30  2:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28  5:36 [gentoo-dev] Non-free software in Gentoo Vincent Launchbury
2009-12-28  8:10 ` Rémi Cardona
2009-12-28 13:11   ` Nirbheek Chauhan
2009-12-29  8:59     ` Peter Volkov
2009-12-29  5:24   ` Vincent Launchbury
2009-12-29  9:02     ` Peter Volkov
2009-12-29 18:32       ` Robin H. Johnson
2009-12-29 23:17         ` Brian Harring
2009-12-28 11:21 ` Jeroen Roovers
2009-12-28 14:37 ` Jeremy Olexa
2009-12-28 18:56 ` Robin H. Johnson
2009-12-28 22:15   ` Richard Freeman
2009-12-28 22:53     ` Robin H. Johnson
2009-12-29  1:16       ` Richard Freeman
2009-12-30  0:52         ` Greg KH
2009-12-30 11:43           ` Richard Freeman
2009-12-31  4:51             ` Greg KH
2009-12-31  6:02               ` Harald van Dijk
2009-12-30  0:50 ` Greg KH
2009-12-30  2:42   ` Vincent Launchbury [this message]
2009-12-31  4:48     ` Greg KH
2009-12-31 12:30       ` Richard Freeman
2010-01-06  4:55       ` Vincent Launchbury
2010-01-06 18:57         ` Greg KH
2010-01-06 21:55           ` Harald van Dijk
2010-01-07  6:19             ` Vincent Launchbury
2010-01-07 14:37               ` Richard Freeman
2010-01-08  5:26               ` Greg KH
2010-01-08 15:48                 ` Richard Freeman

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=4B3ABDFE.9050209@doublecreations.com \
    --to=vincent@doublecreations.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /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