linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filip Van Raemdonck <mechanix@debian.org>
To: Simon Kelley <srk@thekelleys.org.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Simon Kelley <simon@thekelleys.org.uk>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Binary firmware in the kernel - licensing issues.
Date: Wed, 7 May 2003 11:07:00 +0200	[thread overview]
Message-ID: <20030507090700.GD25251@debian> (raw)
In-Reply-To: <3EB8AD41.5010605@thekelleys.org.uk>

On Wed, May 07, 2003 at 07:52:49AM +0100, Simon Kelley wrote:
> Alan Cox wrote:
> >On Maw, 2003-05-06 at 16:42, Simon Kelley wrote:
> >
> >>Then, as you say, I need to know if the kernel developers have given
> >>permission to distribute a work which combines Atmel's blob with
> >>their source.[1]
> >
> >
> >Either the GPL does or it doesn't.
> <snip>
> >Na.. firmware stuff needs sorting out, but from the conversations I've
> >seem so far that involved people with a knowledge of law thats by
> >putting the firmware out of the kernel entirely
> >
> 
> Either the GPL allows this or it doesn't or maybe it is just not clear.
> If it is in fact silent or ambiguous on the issue then Linus is a much 
> more useful resource than Lawyers.

No he isn't.

Others are (re)distributing his kernels, whether heavily patched or not.
When he OKs it while lawyers say it's not, it's getting close to or
completely impossible for those others to include the drivers in the
kernel they redistribute without putting themselves at legal risk.
Effectively making it impossible for those people or organizations to
support running the kernels they distribute on the hardware which needs
that firmware.

While I agree that it is these others own responsibility to make sure
they are not doing anything illegal, Linus' approval contrary to legal
advise would create a situation where there is hardware which has drivers,
but noone can legally redistribute them. This is just as bad as having no
drivers at all.
(Actually, it's worse. Think about the amount of bitching that happens
about distributions not including Nvidia drivers, decss libraries or mp3
players. And you go try explain to aunt Tillie why RH can't include driver
XYZ for her fizzie-whizzie USB gadget while Linus does)

Sure, Linus will also be putting himself at risk in the above situation,
but that's his own call to make. Question yourself whether it's more
likely for Linus to get sued over it or, say, RedHat to get sued.
(Hmm, I wonder about the liability in the above case of kernel.org
mirrors)


Regards,

Filip

-- 
"Perhaps Debian is concerned more about technical excellence rather than
 ease of use by breaking software. In the former we may excel. In the
 latter we have to concede the field to Microsoft. Guess where I want
 to go today?"
	-- Manoj Srivastava

  reply	other threads:[~2003-05-07  8:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 11:38 Binary firmware in the kernel - licensing issues Simon Kelley
2003-05-06 11:15 ` Alan Cox
2003-05-06 13:28   ` Simon Kelley
2003-05-06 12:44     ` Alan Cox
2003-05-06 13:42   ` Simon Kelley
2003-05-06 12:19 ` Matti Aarnio
2003-05-06 15:16   ` J. Bruce Fields
2003-05-06 15:42     ` Simon Kelley
2003-05-06 15:21       ` Alan Cox
2003-05-07  6:52         ` Simon Kelley
2003-05-07  9:07           ` Filip Van Raemdonck [this message]
2003-05-07  9:54             ` Simon Kelley
2003-05-08  8:01               ` Filip Van Raemdonck
2003-05-08  9:44                 ` Simon Kelley
2003-05-08 10:56                   ` Alan Cox
2003-05-06 15:48     ` Richard B. Johnson
2003-05-06 15:19       ` Alan Cox
2003-05-08 10:20 ` Jörn Engel
2003-05-06 12:54 Downing, Thomas
2003-05-06 12:46 ` Alan Cox
2003-05-06 15:04 Adam J. Richter
2003-05-07 11:59 Adam J. Richter
2003-05-07 14:08 ` Simon Kelley
2003-05-07 17:14 Adam J. Richter
2003-05-08 13:20 Downing, Thomas
2003-05-08 15:59 Adam J. Richter
2003-05-08 16:09 ` Jörn Engel
2003-05-08 16:35 Adam J. Richter
2003-05-08 18:26 ` root
2003-05-08 22:19   ` Alan Cox
2003-05-08 16:51 Adam J. Richter
2003-05-08 23:36 Adam J. Richter

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=20030507090700.GD25251@debian \
    --to=mechanix@debian.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon@thekelleys.org.uk \
    --cc=srk@thekelleys.org.uk \
    --cc=torvalds@transmeta.com \
    /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;
as well as URLs for NNTP newsgroup(s).