From: Willy Tarreau <willy@w.ods.org>
To: Ryan Cumming <ryan@spitfire.gotdns.org>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: TG3(Tigoon) & Kernel 2.4.27
Date: Tue, 31 Aug 2004 07:05:19 +0200 [thread overview]
Message-ID: <20040831050519.GE564@alpha.home.local> (raw)
In-Reply-To: <200408301814.41346.ryan@spitfire.gotdns.org>
On Mon, Aug 30, 2004 at 06:14:38PM -0700, Ryan Cumming wrote:
> On Tuesday 24 August 2004 23:36, you 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.
> initramfs?
>
> > 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.
> For GPL compliance, no, that wouldn't work. The GPL states:
> "The source code for a work means the preferred form of the work for making
> modifications to it."
>
> Which is likely C or at least assembly with label names and comments in this
> case.
It would have taken less time for the people who removed the firmware and
will assure support for their users to disassemble this code and put labels
and comments in it. When I was 16, I totally disassembled my PC's bios (8kB)
commented it and labelled it to the point of making it re-assemblable. It
did not take very much time (a week-end), and it was crappy x86 code with
unaligned and mangled code/data + hard-coded stack values for the "calls"
without any RAM usage. Here you have about 2kB of clean MIPS code which is
about 500 instructions (500 lines). I doubt anyone knowing mips assembly
enough would spend more than a week-end putting comments and labels in it.
Now another possibility would be for those zealots to replace the firmware
by an open-source one such as http://alteon.shareable.org/ which BTW contains
all the tools needed for the dirty work.
Anyway, this thread is getting boring...
Regards,
Willy
next prev parent reply other threads:[~2004-08-31 5:05 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
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 [this message]
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=20040831050519.GE564@alpha.home.local \
--to=willy@w.ods.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@spitfire.gotdns.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