linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
	Simon Kelley <simon@thekelleys.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Binary firmware in the kernel - licensing issues.
Date: Tue, 6 May 2003 11:48:20 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0305061139020.6723@chaos> (raw)
In-Reply-To: <20030506151644.GA19898@fieldses.org>

On Tue, 6 May 2003, J. Bruce Fields wrote:

> On Tue, May 06, 2003 at 03:19:54PM +0300, Matti Aarnio wrote:
> > On Tue, May 06, 2003 at 12:38:54PM +0100, Simon Kelley wrote:
> > > I shall contact Atmel for advice and clarification but my question for
> > > the list is, what should I ask them to do? It's unlikely that they will
> > > release the source to the firmware and even if they did I wouldn't want
> > > firmware source  in the kernel tree since the kernel-build toolchain
> > > won't be enough to build the firmware. What permissions do they have to
> > > give to make including this stuff legal and compatible with the rest of
> > > the kernel?
> >
> > Adding a phrase like:  "This firmware binary block is intended to be
> > used in BSD/GPL licensed driver"   would definitely clarify it.
> > Possibly adding:
> >   "Source code/further explanations for this binary block
> >    are available at file FFFF.F / are not available."
>
> It's not Atmel whose permission you need to do this, it's the other
> kernel developers whose permission you need.  By releasing their code
> under the GPL, the people who hold copyright on all the other kernel
> code have essentially given you permission to modify and redistribute
> their code as long as you make source available for the resulting work.
>
> The question is whether adding this binary blob to the linux kernel
> violates the license that the kernel developers gave you.  I can't see
> how Amtel saying it's OK would make it so.
>
> --Bruce Fields

I don't see anybody sending the contents of the PALs, ASICs, and
other components on your motherboard. Modern machines have all
those bits loaded upon power-up. Before the power is applied,
the components aren't even connected. The same is true for
many disk drive boards, screen-card boards, etc. The manufacturer
will supply a bucket of bits, plus instructions on how to
load them into the hardware. I don't see how this violates either
the wording or the spirit of GPL. The manufacturer certainly
isn't going to supply the "source", which is the output of a
graphical program where the Engineers spent the last year
designing the board. If this kind of BS continues, Linux
will go the way of the Hippie culture.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.


  parent reply	other threads:[~2003-05-06 15:34 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
2003-05-08  9:44                 ` Simon Kelley
2003-05-08 10:56                   ` Alan Cox
2003-05-06 15:48     ` Richard B. Johnson [this message]
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=Pine.LNX.4.53.0305061139020.6723@chaos \
    --to=root@chaos.analogic.com \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=simon@thekelleys.org.uk \
    /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).