From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NQD2M-0003mV-KE for garchives@archives.gentoo.org; Thu, 31 Dec 2009 04:53:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 74569E071D; Thu, 31 Dec 2009 04:52:25 +0000 (UTC) Received: from coco.kroah.org (kroah.org [198.145.64.141]) by pigeon.gentoo.org (Postfix) with ESMTP id 36197E071D for ; Thu, 31 Dec 2009 04:52:25 +0000 (UTC) Received: from localhost (unknown [142.131.21.150]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by coco.kroah.org (Postfix) with ESMTPSA id D7E6B48665 for ; Wed, 30 Dec 2009 20:52:19 -0800 (PST) Date: Wed, 30 Dec 2009 20:48:31 -0800 From: Greg KH To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Non-free software in Gentoo Message-ID: <20091231044831.GB28130@kroah.com> References: <4B3843E2.90800@doublecreations.com> <20091230005035.GA21380@kroah.com> <4B3ABDFE.9050209@doublecreations.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B3ABDFE.9050209@doublecreations.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Archives-Salt: 20510594-9bf8-411d-81f1-1829cecc2dc4 X-Archives-Hash: b4a1ebe86c6357df836b9e650253d268 On Tue, Dec 29, 2009 at 09:42:06PM -0500, Vincent Launchbury wrote: > 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. Heh, no, it does not, unless your BIOS, and your keyboard firmware, and your mouse firmware are all under a "free" license. The only thing close to this type of machine is the OLPC, and even then, I don't think all the microcode for the box was ever released. So it's a pointless effort. Hint, these firmware blobs do not run on your processor, so they have nothing to do with the license of your "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. Again, no, the GPLv2 covers the license of all of the code you run in the kernel package. > > 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. And again, you do not run those firmware images on your processor, so the point is moot. And note, _I_ placed those images in the kernel image, after consulting lawyers about this issue, so it's not like I don't know what I am talking about here. > 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. Please see above why this is all just fine. thanks, greg k-h