more on objcopy
Ronald G. Minnich
rminnich at lanl.gov
Wed Feb 5 10:27:00 CET 2003
ok, I think objcoyp is doing the right thing. Whew!
Here are the sections:
[Nr] Name Type Addr Off Size ES Flg Lk
Inf Al
[ 0] NULL 00000000 000000 000000 00 0
0 0
[ 1] .rom PROGBITS ffff4000 001000 002400 00 AX 0
0 8
[ 2] .payload PROGBITS ffff6400 003400 0049b3 00 WA 0
0 1
[ 3] .reset PROGBITS fffffff0 007ff0 000010 00 A 0
0 1
[ 4] .id PROGBITS ffffffd3 007fd3 00001d 00 A 0
0 1
[ 5] .text PROGBITS fffffff0 007ff0 000000 00 AX 0
0 4
[ 6] .data PROGBITS fffffff0 007ff0 000000 00 WA 0
0 4
[ 7] .bss NOBITS fffffff0 008ff0 000000 00 WA 0
0 4
[ 8] .shstrtab STRTAB 00000000 008ff0 000045 00 0
0 1
[ 9] .symtab SYMTAB 00000000 0091f0 0010e0 10 10
bf 4
[10] .strtab STRTAB 00000000 00a2d0 0010f8 00 0
0 1
The .rom starts at 0xffff4000, which gives you a 49152-byte section.
I think the .ldscript is giving a fixed-size linuxbios without regard to
how big it actually is, which means tuning via things like max log
message etc. is no longer a real option. It also means my etherboot, which
is 17K, no longer fits together with linuxbios into 64K.
OK, back to the drawing board :-)
ron
More information about the coreboot
mailing list