From: neroden@fastmail.fm (Nathanael Nerode)
To: davem@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: TG3(Tigoon) & Kernel 2.4.27
Date: Mon, 30 Aug 2004 18:16:38 -0400 [thread overview]
Message-ID: <20040830221638.GA3596@fastmail.fm> (raw)
David S. Miller wrote:
>The tg3 firmware is just a bunch of MIPS instructions.
Well, good to know that. It's the first I'd heard of it.
>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.
Before you blithely made this claim, you should have actually tried running
objdump --disassemble on the image.
It's not packed up in a standard ELF/COFF/etc format, so that doesn't
actually work. You can use simple assembler trickery to pack it up into a
normal object file *if* you have an assembler for mips *and* you know whether
the chip is running little-endian or big-endian (I have no idea). You may
need other information as well. :-P Then and only then can you try to
dissassemble it with objdump. Then you have to separate data in the text
section out from the code in order to get something which actually
approximates source code.
Much simpler for Broadcom to just release the source code. :-P
--
This space intentionally left blank.
next reply other threads:[~2004-08-30 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 22:16 Nathanael Nerode [this message]
2004-08-30 22:23 ` TG3(Tigoon) & Kernel 2.4.27 Jeff Garzik
2004-08-30 22:31 ` David S. Miller
2004-08-30 22:32 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 15:13 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
2004-08-25 7:40 ` Laurent CARON
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=20040830221638.GA3596@fastmail.fm \
--to=neroden@fastmail.fm \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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