bootloader & head.S weirdness & restructuring

[Michael Schmitz]

> I don't think this would work in all cases, although it would be great if
> we could do it.  We can't stomp on the interrupt vectors at physical 0
> because chrp/pmac need them to do the early OF calls to setup things and
> copy the device tree before we can safely stomp on physical 0.  If the

How much of space at physical 0 do you need to leave alone? I'm thinking
about leaving a gap of some k between _start and _stext for that, and
making all boot loaders load the kernel to physical 0 (skipping the part
up to _stext), and jump to _stext. 

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/