From: Chris Cheney <ccheney@cheney.cx>
To: debian-devel@lists.debian.org
Cc: Adrian Bunk <bunk@fs.tum.de>,
239952@bugs.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 16:54:23 -0600 [thread overview]
Message-ID: <20040325225423.GT9248@cheney.cx> (raw)
In-Reply-To: <20040325220803.GZ16746@fs.tum.de>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Thu, Mar 25, 2004 at 11:08:03PM +0100, Adrian Bunk wrote:
> There's another issue with these files:
>
<-- snip -->
>
> The GPL says that you must give someone receiving a binary the source
> code, and it says:
> The source code for a work means the preferred form of the work for
> making modifications to it.
>
>
> This is perhaps a bit besides the main firmware discussion and IANAL,
> but is this file really covered by the GPL?
IMHO code that can be compiled would probably be the preferred form
of the work. The source to the firmware in many cases and probably even
this one is very unlikely to be able to be compiled under Linux at all.
Also, unless the driver is written by the company producing the hardware
itself even the author will likely not have the source code to the
firmware and will only have a binary form (think reverse engineering).
IMHO a driver for a piece of hardware does not include the software that
the hardware itself is running, just the software that the primary CPU
itself is running. YMMV.
Chris
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-25 23:00 UTC|newest]
Thread overview: 45+ 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 ` Stefan Smietanowski
2004-03-26 0:33 ` John Hasler
2004-03-26 0:17 ` David Woodhouse
2004-03-26 1:30 ` John Hasler
2004-03-26 8:50 ` Stefan Smietanowski
2004-03-26 9:43 ` Dumitru Ciobarcianu
2004-03-26 10:14 ` Stefan Smietanowski
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: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 [this message]
2004-03-26 0:41 ` David Schwartz
2004-03-26 9:09 ` John Bradford
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:38 ` Stefan Smietanowski
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: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
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=20040325225423.GT9248@cheney.cx \
--to=ccheney@cheney.cx \
--cc=239952@bugs.debian.org \
--cc=bunk@fs.tum.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox