From: Stefan Smietanowski <stesmi@stesmi.com>
To: Giuliano Pochini <pochini@shiny.it>
Cc: David Schwartz <davids@webmaster.com>,
linux-kernel@vger.kernel.org, Adrian Bunk <bunk@fs.tum.de>
Subject: Re: Binary-only firmware covered by the GPL?
Date: Fri, 26 Mar 2004 12:55:49 +0100 [thread overview]
Message-ID: <40641A45.2060100@stesmi.com> (raw)
In-Reply-To: <XFMail.20040326122022.pochini@shiny.it>
Giuliano Pochini wrote:
> On 26-Mar-2004 David Schwartz wrote:
>
>
>>As for "another processor", another from what processor? There is just this
>>one file. We have here a file that is allegedly distributed under the terms
>>of the GPL. It is, however, obfuscated and not the preferred form for making
>>modifications.
>
>
> It's my turn to make flames grow higher :)
> And about binary data which is not executed by any processor ? Some
> cards have ASIC chips that must be programmed to make the card do
> something other than consuming power. That "code" is *not* a program
> and it's always shipped in binary form.
Shipped - yes, but how is it modified (ie edited) ?
Using a special program? That's fine then. Using a hex editor? That's
also fine. Using a VHDL compiler ? Then they need to give out the VHDL
code to it I believe. But hell, what do I know, when moving over to
hardware it's uncertain how the GPL would apply, at least to me,
and of course IANAL.
// Stefan
next prev parent reply other threads:[~2004-03-26 11:56 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 [this message]
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 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=40641A45.2060100@stesmi.com \
--to=stesmi@stesmi.com \
--cc=bunk@fs.tum.de \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pochini@shiny.it \
/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