linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filip Van Raemdonck <mechanix@debian.org>
To: Simon Kelley <simon@thekelleys.org.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.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: Thu, 8 May 2003 10:01:16 +0200	[thread overview]
Message-ID: <20030508080116.GD15296@debian> (raw)
In-Reply-To: <3EB8D7D9.7070304@thekelleys.org.uk>

On Wed, May 07, 2003 at 10:54:33AM +0100, Simon Kelley wrote:
> 
> Now Linus could say "I consider that the kernel copyright holders 
> did/didn't give permission to combine  their work with firmware blobs" 
> and I contend that practically all the copyright holders would go along
> with that judgement, just as they went along with Linus's judgement
> about linking binary-only modules with their work.

It's been pointed out repeatedly that there are a few which disagree with
this; they just did not feel compelled (yet?) into action over it.

But there is an important difference in binary modules vs binary
firmware blobs.

In the modules case, it's the binary modules provider which exposes
himself to legal issues.
In the firmware case, you are exposing the kernel itself to IP liability
issues. Do you really want that? (Think SCO)


Regards,

Filip

-- 
"There is a 90% chance that this message was written when the author's been
 up longer than he should have. Please disregard any senseless drivel."
	-- Chris Armstrong

  reply	other threads:[~2003-05-08  7:48 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
2003-05-07  9:54             ` Simon Kelley
2003-05-08  8:01               ` Filip Van Raemdonck [this message]
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=20030508080116.GD15296@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=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).