From: Dumitru Ciobarcianu <Dumitru.Ciobarcianu@iNES.RO>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Jeff Garzik <jgarzik@pobox.com>, Adrian Bunk <bunk@fs.tum.de>,
239952@bugs.debian.org, debian-devel@lists.debian.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Bug#239952: Binary-only firmware covered by the GPL?
Date: Fri, 26 Mar 2004 11:43:28 +0200 [thread overview]
Message-ID: <1080294208.27237.2.camel@LNX.iNES.RO> (raw)
In-Reply-To: <4063EEC1.9080203@stesmi.com>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On Fri, 2004-03-26 at 09:50 +0100, Stefan Smietanowski wrote:
> /*
> This file is under the GPL, yada yada
> */
> #include "things.h"
>
> void some_func(void)
> {
> does_something();
> }
>
> char firmware[]={0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07};
>
> void upload_firmware(void)
> {
> do_upload(firmware);
> }
>
> --
>
> Then it seems clear to me that the firmware is under the GPL because it
> is PART of the GPL'd file.
If you're right, then the "binary" of the firmware it's GPL, not the
source of the firmware, because that's what you have in this case :)
You can have that ? GPL the binary but not the source ? :)
--
Cioby
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-26 9:43 UTC|newest]
Thread overview: 36+ 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-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 [this message]
2004-03-26 10:14 ` Stefan Smietanowski
2004-03-26 0:33 ` Bug#239952: " 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-25 22:54 ` Chris Cheney
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 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
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=1080294208.27237.2.camel@LNX.iNES.RO \
--to=dumitru.ciobarcianu@ines.ro \
--cc=239952@bugs.debian.org \
--cc=bunk@fs.tum.de \
--cc=debian-devel@lists.debian.org \
--cc=dwmw2@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stesmi@stesmi.com \
/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