linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: root@mauve.demon.co.uk
To: adam@yggdrasil.com (Adam J. Richter)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Binary firmware in the kernel - licensing issues.
Date: Thu, 8 May 2003 19:26:07 +0100 (BST)	[thread overview]
Message-ID: <200305081826.TAA04803@mauve.demon.co.uk> (raw)
In-Reply-To: <200305081635.h48GZk007160@adam.yggdrasil.com> from "Adam J. Richter" at May 08, 2003 09:35:46 AM

<snip>
> 
> 	Let's be clear: embedding binary firmware into a GPL'ed
> work is fine if the firmware contains no additional restriction
> beyond the GPL and complete source code for the firmware is
> included.  I think you understand this much already, but I just
> want to be clear about it.

> 	All three distribution options in section 3 of the version 2
> of the GNU General Public License require distribution or arrangments
> for distribution "machine-readable source code", and defines
> "source code" as "the preferred form of the work for making
> modifications to it."  That seems pretty clear to me.

So if you've got a CPU, that you have to load the microcode into before
fully booting, you can't run linux on it natively, unless the CPU maker
provides full microcode source? 
Presumably the "preferred form" clause would mean that there must 
be hardware documentation too.

And when is a binary a binary, and not a string constant?

  reply	other threads:[~2003-05-08 18:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 16:35 Binary firmware in the kernel - licensing issues Adam J. Richter
2003-05-08 18:26 ` root [this message]
2003-05-08 22:19   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 23:36 Adam J. Richter
2003-05-08 16:51 Adam J. Richter
2003-05-08 15:59 Adam J. Richter
2003-05-08 16:09 ` Jörn Engel
2003-05-08 13:20 Downing, Thomas
2003-05-07 17:14 Adam J. Richter
2003-05-07 11:59 Adam J. Richter
2003-05-07 14:08 ` Simon Kelley
2003-05-06 15:04 Adam J. Richter
2003-05-06 12:54 Downing, Thomas
2003-05-06 12:46 ` Alan Cox
2003-05-06 11:38 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
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

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=200305081826.TAA04803@mauve.demon.co.uk \
    --to=root@mauve.demon.co.uk \
    --cc=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).