From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Stefan Smietanowski <stesmi@stesmi.com>,
Eduard Bloch <edi@gmx.de>, David Schwartz <davids@webmaster.com>,
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: 30 Mar 2004 20:11:14 +0200 [thread overview]
Message-ID: <874qs6nr25.fsf@mrvn.homelinux.org> (raw)
In-Reply-To: <20040330113915.GB3084@openzaurus.ucw.cz>
Pavel Machek <pavel@suse.cz> writes:
> Hi!
>
> If my code contains picture of human, do I have to provide his DNA, too?
> Pavel
>
> (runs away)
If the picture was made with gimp and you keep an xcf of it around for
changing it (because it keeps the layers) but only ship a png (no more
layers) then your violating the GPL.
Prefered form for you would be the xcf file and not the png.
Of cause its hard to show that you do use an xcf as prefered form
without spying at you working on it so you can get away with an png.
With binary firmware is way easier to argue that the prefered form is
some kind of asm, C , forth or whatever source and not the binary.
That someone is prefering a hex editor is very unlikely.
If the driver+firmware is released as GPL (say as binary driver
containing the firmware) then the _firmware_ would be in violation of
the GPL unless source is provided or a note confirming the 3 years on
request thing is there. Either way the source of the firmware has to
be made available.
So please do get firms to release GPLed drivers with firmware included
as GPL bcause then we can sue them for the firmware source. :)
MfG
Goswin
next prev parent reply other threads:[~2004-03-30 18:11 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 ` 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
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 [this message]
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=874qs6nr25.fsf@mrvn.homelinux.org \
--to=brederlo@informatik.uni-tuebingen.de \
--cc=davids@webmaster.com \
--cc=debian-devel@lists.debian.org \
--cc=edi@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pavel@suse.cz \
--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
all inboxes | Powered by JetHome®