From: Eric <eric@cisu.net>
To: Christoph Hellwig <hch@lst.de>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Tue, 15 Jun 2004 19:38:02 -0500 [thread overview]
Message-ID: <200406151938.02613.eric@cisu.net> (raw)
In-Reply-To: <20040615205753.GA24380@lst.de>
On Tuesday 15 June 2004 03:57 pm, Christoph Hellwig wrote:
> While I don't want to jump into the usual Debian wankfest whether Linux
> as GPL'ed project can distribute hex-images of firmware at all there are
> a few firmware C headers files that have a license statement that aren't
> GPL-compatible at all, namely the keyspan firmware in
> drivers/usb/serial/keyspan*_fw.h with the following license text:
--*snip*--
> 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.
> 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."
> ---------------------------- snip ----------------------------
>
> which makes the kernel as whole unredistributable. A similar license
> was according to Greg also recently granted for
> drivers/usb/misc/emi62_fw_*.h which currently has even worse license
> statements in there.
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.
Please correct me if I am wrong.
next prev parent reply other threads:[~2004-06-16 0:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 20:57 more files with licenses that aren't GPL-compatible Christoph Hellwig
2004-06-16 0:38 ` Eric [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
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=200406151938.02613.eric@cisu.net \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.