From: Joshua Kwan <joshk@triplehelix.org>
To: "David S. Miller" <davem@redhat.com>
Cc: rddunlap@osdl.org, lcaron@apartia.fr, linux-kernel@vger.kernel.org
Subject: Re: TG3(Tigoon) & Kernel 2.4.27
Date: Wed, 25 Aug 2004 00:47:57 -0700 [thread overview]
Message-ID: <412C442D.3090107@triplehelix.org> (raw)
In-Reply-To: <20040824233648.53eb7c30.davem@redhat.com>
David S. Miller wrote:
> I pity the poor fool who wishes to netboot his system using
> a tg3 card and use an nfsroot with Debian. Kind of hard to
> get the card firmware from the filesystem in that case.
For the record, I made this change to Debian's kernel source, because
the project consensus was that the firmware blobs were not free
according to Debian's Free Software Guidelines.
Now I hope you're also aware that tg3 without the firmware works for
about ~90-95% of all tigon3 based devices.
Anyway, to tell you the truth, I would have preferred not making this
change. But the alternative was impossible: sticking the kernel into our
non-free section. See below for more.
> I guess these debian kernel folks replace the BIOS on their
> system with one they have the sources for as well.
Nope. Good ol' Award is fine enough for me.
Then again, LinuxBIOS would satisfy the need for source, wouldn't it?
;)
> The tg3 firmware is just a bunch of MIPS instructions.
> I guess if I ran objdump --disassemble on the image and
> used the output of that in the tg3 driver and "compiled
> that source" they'd be happy. And this makes the situation
> even more ludicrious.
I'm curious: run that by debian-legal@lists.debian.org and see what they
say. They're the folks who started all this.
As far as I'm personally concerned, as long as Linus/Marcelo thinks it's
free (i.e. it can be found in BK) and no one but people in Debian have
the boredom/presence of mind/whatever to point out that this breaks our
software guidelines, I find myself siding with the majority who believe
it's free enough. The linux-kernel community seems to be actively
cracking down on blatant GPL violations (see: Linksys WRT54G), and
that's good, but they (perhaps wisely) seem to have overlooked the
supposed firmware-in-file issue, and I figure that does say something.
I'm not clear on the details but what they seem to have deduced is that
as long as the firmware 'variable' is not shipped into Debian as part of
the compiled tg3.o, it's barely Free. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=243044
for details of the loophole. To me, it makes no difference...
Interesting to know that it's a "bunch of MIPS instructions." I'd wager
that eventually, some enterprising, bored hacker would probably come up
with a glorious Free cleanroom implementation of the firmware that you
need to use a MIPS assembler or C comiler on on at build time.. (AIUI
there's already some of that stuff in linux-2.6, though they're actually
the original source code.)
As I said it's all very disgusting (hmm.. déjà vu..) and maybe people
will stop caring about it someday.
--
Joshua Kwan
next prev parent reply other threads:[~2004-08-25 7:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 15:13 TG3(Tigoon) & Kernel 2.4.27 Laurent CARON
2004-08-24 16:25 ` Randy.Dunlap
2004-08-24 18:34 ` David S. Miller
2004-08-25 1:37 ` Joshua Kwan
2004-08-25 3:17 ` Randy.Dunlap
2004-08-25 4:02 ` Joshua Kwan
2004-08-25 4:45 ` Willy Tarreau
2004-08-25 6:36 ` David S. Miller
2004-08-25 7:47 ` Joshua Kwan [this message]
2004-08-25 8:34 ` Oliver Neukum
2004-08-25 19:03 ` David S. Miller
2004-08-31 1:14 ` Ryan Cumming
2004-08-31 1:33 ` David S. Miller
2004-08-31 5:05 ` Willy Tarreau
2004-08-25 7:40 ` Laurent CARON
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 22:16 Nathanael Nerode
2004-08-30 22:23 ` Jeff Garzik
2004-08-30 22:31 ` David S. Miller
2004-08-30 22:32 ` Andreas Schwab
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=412C442D.3090107@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=davem@redhat.com \
--cc=lcaron@apartia.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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