[PATCH 8/15] zImage: Cleanup and improve zImage entry point
Scott Wood
scottwood at freescale.com
Sat Mar 17 03:21:35 EST 2007
On Fri, Mar 16, 2007 at 11:50:16AM +1100, David Gibson wrote:
> Sorry, I misunderstood. That sort of firmware - and the even dumber
> sort where the start address isn't configurable at all - is exactly
> what option (1) is for. You'll need an asm platform file which
> defines _zimage_start to a fixed offset. In your case you could
> probably just make it a jump to the generic _zimage_start.
One problem with that is that the wrapper currently only accepts one
platform .o file -- and presumably one isn't going to want to do all of
the platform code in assembly.
If the wrapper is changed to allow two platform .o files, then the link
order can be "platform_early.o crt0.o platform.o". If platform_early.o
isn't provided, then crt0.o goes first, and one doesn't need to provide a
platform .S for the special case of having the entry be at a known offset
from the start of the file, while still allowing a platform .S to be
provided for cases where it's really needed.
-Scott
More information about the Linuxppc-dev
mailing list