On Tue, Oct 18, 2011 at 2:11 PM, Stephen Warren swarren@nvidia.com wrote:
uImage files contain absolute "load" and "entry" addresses. Such a concept is incompatible with using the same kernel image on multiple SoCs, each with a potentially different SDRAM base. To support that, create a new image type IH_TYPE_KERNEL_REL, which is handled identically to IH_TYPE_KERNEL, except that the "load" and "entry" properties are an offset from the base of SDRAM, rather than an absolute address.
v2:
- Add IH_TYPE_FLATDT_REL.
- Expanded documentation of "an offset from the base of SDRAM".
- Put all new code under #ifdef CONFIG_SYS_RELATIVE_IMAGEs, to prevent code
bloat for platforms not wanting this feature. For me, this still results in a 32-byte .text increase; I'm not sure why.
- A few trivial cleanups (now completely checkpatch clean).
- Tested with MAKEALL -a arm; as best I can tell, this introduces no new
issues.
Signed-off-by: Stephen Warren swarren@nvidia.com
I tested this on Seaboard with CONFIG_SYS_SDRAM_BASE set to 0x100.
The board side works fine but as discussed you need to sort out the HOSTCFLAGS to make it build 'mkimage' correctly.
Regards, Simon