TG3(Tigoon) & Kernel 2.4.27
Quoted 1 line · David S. Miller
The tg3 firmware is just a bunch of MIPS instructions.
Well, good to know that. It's the first I'd heard of it.
Quoted 4 lines
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
Signature · 1 line
This space intentionally left blank.
Quoted 7 lines · Nathanael Nerode
Quoted 1 line · David S. Miller
The tg3 firmware is just a bunch of MIPS instructions.
Well, good to know that. It's the first I'd heard of it.
Much simpler for Broadcom to just release the source code. :-P
The previous generation of devices, driven by the acenic driver, actually had a firmware kit that was available to lucky parties. Included full firmware source, that you could tweak to your heart's delight.
Jeff
Quoted 7 lines · On Mon, 30 Aug 2004 18:16:38 -0400 [email protected] (Nathanael Nerode) wrote:
Quoted 4 lines
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.
I was speaking abstractly. It is well definted which parts of the hex arrays are the data, bss, and text sections. It doesn't take a rocket scientist to reconstruct things.
Quoted 5 lines · [email protected] (Nathanael Nerode) writes:
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.
You don't have to pack it up, objdump can also disassemble raw data (with --target=binary, --disassemble-all and suitable --architecture).
Andreas.
Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected] SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."