mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: <oliver@neukum.org>
Cc: <erikharrison@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: RE: more files with licenses that aren't GPL-compatible
Date: Wed, 16 Jun 2004 16:45:28 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKIELGMKAA.davids@webmaster.com> (raw)
In-Reply-To: <200406170045.32844.oliver@neukum.org>


> Am Mittwoch, 16. Juni 2004 23:21 schrieb David Schwartz:

> >     b) You must cause any work that you distribute or publish, that in
> >     whole or in part contains or is derived from the Program or any
> >     part thereof, to be licensed as a whole at no charge to all third
> >     parties under the terms of this License.
> >

> >         How can you cause the Linux kernel combined with this
> > firmware to be
> > licensed under the terms of the GPL? (And, by the way, I think this
> > prohibits trademark as well, which is very interesting.)

> This all boils down to the question of whether fimware is code or not.

	Perhaps I'm missing something. Can you explain why you think that matters?
I'll repeat the GPL section I'm talking about:

     b) You must cause any work that you distribute or publish, that in
     whole or in part contains or is derived from the Program or any
     part thereof, to be licensed as a whole at no charge to all third
     parties under the terms of this License.

	First, this says, "any work", it's not limited to code. It says, "in whole
or in part contains or is derived from the Program" -- a binary of the Linux
kernel is clearly derived from the Linux kernel source. And it says
"licensed *as a whole* ... under the terms of *this* license".

	So where's the gray area you seem to be imagining?

> As this question is extremely unlikely to be resolved on this list and
> was discussed here several times already, I kindly request that
> you take this discussion to a legalistic list and confine traffic of this
> kind on this list to clear and technical issues.

	This is a different issue. This isn't about distributing firmware and
whether the firmware itself is a derived work. This is about distributing
the Linux kernel as a work containing non-GPL'd elements with use
restrictions. GPL section 2b authoritatively prohibits this. There is no
gray area here.

	This is a clear issue, but not a technical one. However, being unable to
distribute binaries of the Linux kernel would present numerous technical
problems.

	DS



  reply	other threads:[~2004-06-16 23:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 20:57 Christoph Hellwig
2004-06-16  0:38 ` Eric
2004-06-16  1:27   ` Kyle Moffett
2004-06-16  4:11   ` David Schwartz
2004-06-16 20:34     ` Erik Harrison
2004-06-16 20:37       ` Christoph Hellwig
2004-06-16 21:21       ` David Schwartz
2004-06-16 22:45         ` Oliver Neukum
2004-06-16 23:45           ` David Schwartz [this message]
2004-06-17 14:09             ` Timothy Miller
2004-06-17 18:35               ` David Schwartz
2004-06-17 19:22                 ` Timothy Miller
2004-06-17  7:59           ` Christoph Hellwig
2004-06-17  8:43             ` Oliver Neukum
2004-06-17  8:47               ` Christoph Hellwig
2004-06-17 10:09             ` Martin Diehl
2004-06-17 10:14               ` Christoph Hellwig
2004-06-19 18:29               ` David Woodhouse
2004-06-17 14:04           ` Timothy Miller
2004-06-16 22:49       ` Helge Hafting
2004-06-18  9:08         ` Adrian Cox
2004-06-18 11:21           ` Kyle Moffett
2004-06-16 23:47 Wichmann, Mats D
2004-06-17  1:18 ` Kyle Moffett
2004-06-18  6:29 Adam J. Richter
2004-06-17 15:44 ` Michael Poole
2004-06-17 17:09   ` Adam J. Richter
2004-06-17 19:14     ` Kyle Moffett
2004-06-17 20:51       ` Flavio Stanchina
2004-06-17 20:53         ` Kyle Moffett
2004-06-17 21:05         ` mdpoole
2004-06-17 21:10           ` Christoph Hellwig
2004-06-17 21:45           ` Flavio Stanchina
2004-06-17 20:22     ` mdpoole
2004-06-17 18:05 ` Greg KH
2004-06-17 19:54   ` Christoph Hellwig
2004-06-17 20:22     ` Greg KH
2004-06-17 20:30       ` Christoph Hellwig
2004-06-17 20:52         ` Greg KH
2004-06-18  6:56 Adam J. Richter
2004-06-18 11:09 ` mdpoole

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=MDEHLPKNGKAHNMBLJOLKIELGMKAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=erikharrison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.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

all inboxes | Powered by JetHome®