[PATCH 01/11] [POWERPC] bootwrapper: Allow specifying of image physical offset
Kumar Gala
galak at kernel.crashing.org
Wed Apr 2 08:52:49 EST 2008
On Apr 1, 2008, at 5:08 AM, Paul Mackerras wrote:
> Kumar Gala writes:
>
>> Normally we assume kernel images will be loaded at offset 0. However
>> there are situations, like when the kernel itself is running at a
>> non-zero
>> physical address, that we don't want to load it at 0.
>>
>> Allow the wrapper to take an offset. We use this when building u-
>> boot images.
>
> This makes it a bit harder to build a kernel and then wrap it later
> on, since one would have to know what -m value to give. Would it
> possible for either the wrapper script or mkimage to peek in the ELF
> header of the vmlinux to work out what physical address to use?
Hmm, need to think about that. But my initial reaction is two fold.
One I don't think this information would be around and two don't we
already have this problem with a kdump kernel?
- k
More information about the Linuxppc-dev
mailing list