linux-mips
[Top] [All Lists]

Moving kernel_entry to LOADADDR

To: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Moving kernel_entry to LOADADDR
From: Gerald Champagne <gerald.champagne@esstech.com>
Date: Thu, 18 Oct 2001 19:58:58 -0500
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012
I'm planning to work with a very minimal boot loader, and I'd like
to hard-code a jump to kernel_entry in my boot loader.  I got tired
of having kernel_entry moving around, so I just moved it to the top
of head.S, just afte the ".fill 0x280".  That places kernel_entry at
the same place every time.  It's always at LOADADDR+0x280.

But wait a minute... the 0x280 is there to leave room for the exception
vectors.  Doesn't that only make sense if LOADADDR=0x80000000?  Isn't
this allocating the space for the exception vectors twice?  Why not
remove the .fill, then the kernel entry point will always be exactly
LOADADDR?  This would break any configuration that has LOADADDR=0x80000000,
but the only configuration like that is CONFIG_ALGOR_P4032, and that could
easily be modified to LOADADDR=0x80000280 to get the same effect.

I also removed the .fill, and now kernel_entry is always exactly LOADADDR,
and that makes my bootloader easier to maintain.

Is this worth changing in cvs, or did I miss something?

Thanks.

Gerald


<Prev in Thread] Current Thread [Next in Thread>