On Thu, 28 Oct 2004, Li-Ta Lo wrote:
BTW, if you specify the -g option for gcc, you can use the -S option
in objdump to see the source code with the disassebmly (-d).
BTW, this is a very usefull tip. I had been using it lately all the time
to trace ooops in kernel.
objdump -S -C
On Fri, 2004-10-29 at 15:57, [EMAIL PROTECTED] wrote:
On Thu, 2004-10-28 at 16:03, [EMAIL PROTECTED] wrote:
It seems that LinuxBIOS copies itself to _RAMBASE, which is 0x4000.
Then it branches to 0x4000 into _start, which sets up the stack and
calls hardwaremain. The address of
On Tue, 26 Oct 2004 [EMAIL PROTECTED] wrote:
Can someone tell me what the starting sequence is with LinuxBIOS?
Reset jumps to crt0.s. crt0.s calls auto.E. auto.E is built using
romcc, so source-level debugging is not possible.
ah well :-)
The statement
locations can be
On Thu, 2004-10-28 at 16:03, [EMAIL PROTECTED] wrote:
It seems that LinuxBIOS copies itself to _RAMBASE, which is 0x4000.
Then it branches to 0x4000 into _start, which sets up the stack and
calls hardwaremain. The address of hardwaremain from linuxbios_c.o is
wrong. The address is not the
4 matches
Mail list logo
