From: John Hasler <john@dhh.gt.org>
To: 239952@bugs.debian.org, debian-devel@lists.debian.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Binary-only firmware covered by the GPL?
Date: Thu, 25 Mar 2004 19:30:12 -0600 [thread overview]
Message-ID: <8765csbdjv.fsf@toncho.dhh.gt.org> (raw)
In-Reply-To: <1080260235.3643.103.camel@imladris.demon.co.uk> (David Woodhouse's message of "Fri, 26 Mar 2004 00:17:15 +0000")
David Woodhouse writes:
> The firmware blob in question can be reasonably considered to be an
> independent and separate work in itself. The GPL doesn't apply to it when
> it is distributed as a SEPARATE work. But when you distribute it as part
> of a whole which is a work based on other parts of the kernel, by
> including it in the kernel source...
So don't. Put it in a seperate file and load it at boot time.
--
John Hasler You may treat this work as if it
john@dhh.gt.org were in the public domain.
Dancing Horse Hill I waive all rights.
Elmwood, Wisconsin
next prev parent reply other threads:[~2004-03-26 1:24 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1B6Izr-0002Ai-00@r063144.stusta.swh.mhn.de>
[not found] ` <20040325082949.GA3376@gondor.apana.org.au>
2004-03-25 22:08 ` Binary-only firmware covered by the GPL? Adrian Bunk
2004-03-25 22:31 ` Jeff Garzik
2004-03-25 22:47 ` Adrian Bunk
2004-03-25 22:53 ` Bug#239952: " Stefan Smietanowski
2004-03-25 22:53 ` Stefan Smietanowski
2004-03-26 0:33 ` John Hasler
2004-03-26 0:17 ` David Woodhouse
2004-03-26 1:30 ` John Hasler [this message]
2004-03-26 8:50 ` Stefan Smietanowski
2004-03-26 9:43 ` Bug#239952: " Dumitru Ciobarcianu
2004-03-26 9:43 ` Dumitru Ciobarcianu
2004-03-26 10:14 ` Stefan Smietanowski
2004-03-26 0:33 ` Bug#239952: " Matthew Wilcox
2004-03-26 0:33 ` Matthew Wilcox
2004-03-26 1:07 ` GOTO Masanori
2004-03-26 1:39 ` John Hasler
2004-03-26 2:06 ` David Schwartz
2004-03-26 2:06 ` David Schwartz
2004-03-26 2:59 ` Chris Cheney
2004-03-26 3:23 ` John Hasler
2004-03-26 8:53 ` Stefan Smietanowski
2004-03-26 9:12 ` John Bradford
2004-03-26 13:59 ` John Hasler
2004-03-27 9:19 ` John Bradford
2004-03-26 0:41 ` David Schwartz
2004-03-26 11:20 ` Giuliano Pochini
2004-03-26 11:55 ` Stefan Smietanowski
2004-03-25 22:54 ` Chris Cheney
2004-03-26 0:41 ` David Schwartz
2004-03-26 0:41 ` David Schwartz
2004-03-26 9:09 ` John Bradford
2004-03-26 9:09 ` John Bradford
2004-03-26 13:16 ` Eduard Bloch
2004-03-26 13:16 ` Eduard Bloch
2004-03-26 14:19 ` Stefan Smietanowski
2004-03-26 14:29 ` Eduard Bloch
2004-03-26 14:29 ` Eduard Bloch
2004-03-26 14:38 ` Stefan Smietanowski
2004-03-26 14:55 ` Eduard Bloch
2004-03-26 14:55 ` Eduard Bloch
2004-03-26 15:03 ` Stefan Smietanowski
2004-03-26 15:10 ` Matthew Wilcox
2004-03-26 15:22 ` Guy
2004-03-26 15:22 ` Guy
2004-03-26 15:53 ` Gabor Gombas
2004-03-26 21:57 ` Valdis.Kletnieks
2004-03-30 11:39 ` Pavel Machek
2004-03-30 14:02 ` Stefan Smietanowski
2004-03-30 18:11 ` Goswin von Brederlow
2004-04-02 20:53 ` Pavel Machek
2004-03-26 15:04 Matt Reuther
2004-03-26 15:20 ` Matthew Garrett
2004-03-26 22:10 ` David Schwartz
[not found] <8RnZwD.A.91B.qHYaAB@murphy>
2004-03-30 14:57 ` Humberto Massa
2004-03-30 16:51 ` Henning Makholm
2004-03-30 16:51 ` Henning Makholm
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=8765csbdjv.fsf@toncho.dhh.gt.org \
--to=john@dhh.gt.org \
--cc=239952@bugs.debian.org \
--cc=debian-devel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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.