From: Kyle Moffett <mrmacman_g4@mac.com>
To: eric@cisu.net
Cc: Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Tue, 15 Jun 2004 21:27:53 -0400 [thread overview]
Message-ID: <63301070-BF34-11D8-95EB-000393ACC76E@mac.com> (raw)
In-Reply-To: <200406151938.02613.eric@cisu.net>
On Jun 15, 2004, at 20:38, Eric wrote:
> On Tuesday 15 June 2004 03:57 pm, Christoph Hellwig wrote:
>> Permission is hereby granted for the distribution of this firmware
>> image as part of a Linux or other Open Source operating system kernel
>> in text or binary form as required.
Permission is legally granted
>> This firmware may not be modified and may only be used with
>> Keyspan hardware. Distribution and/or Modification of the
>> keyspan.c driver which includes this firmware, in whole or in
>> part, requires the inclusion of this statement."
But we can't actually distribute this file under GPL because we are
not allowed to modify it. They own the copyright, so they can release
it
under any terms that they want. One of their terms is that we can make
copies and give them to people. The other term is that nobody but them
can change it. The two aren't incompatible, but the second is anti-GPL.
> Unredistributable? Am I mistaken? It says permission is given to
> redistribute
> this piece as part of the linux kernel. You just can't modify it.
> Although it
> is unquestionably not a very permissive license, it's inclusion is not
> detrimental to the kernel.
Unfortunately the GPL requires that everybody has the right to *modify*
and
distribute *modified* copies of any files released under it. If a file
is to be
distributed as a part of the GPLed Linux kernel must also follow GPL.
The relevant portion of the GPL:
> [...snip...]
>
> You may modify your copy or copies of the Program or any portion of
> it, thus
> forming a work based on the Program, and copy and distribute such
> modifications or work under the terms of Section 1 above, provided
> that you
> also meet all of these conditions:
>
> [...snip...]
>
> 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.
>
> [...snip...]
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2004-06-16 1:27 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 [this message]
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
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=63301070-BF34-11D8-95EB-000393ACC76E@mac.com \
--to=mrmacman_g4@mac.com \
--cc=eric@cisu.net \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®