[U-Boot] [PATCH v2 3/3] image: Allow images to indicate they're loadable at any address

[Stephen Warren <swarren@nvidia.com>]

On 11/07/2011 04:10 PM, Wolfgang Denk wrote:
> Dear Stephen Warren,
> 
> In message <4EB85EA6.3000106@nvidia.com> you wrote:
>>
>>> and we have to add additional configuration information to the boot
>>> loader.
>>
>> Sorry, I'm unclear what "additional configuration information" needs to
>> be added to the boot-loader, and which of cases (1) and (2) that
>> statement applies to.
> 
> You must define the load address and the entry point address somewhere
> in the U-Boot environment or "U-Boot scripts", as you tend to call it.

The commands in the U-Boot environment need to define some location to
fat/ext/...load the image to either way.

The U-Boot environment never has to define the final address where the
kernel is copied to by bootm. With unmodified ToT U-Boot that absolute
address comes directly from the image's load address field. With my
first patches, that absolute address is calculated from the image's load
address field. With my latest patches, that address is calculated as
wherever the U-Boot environment happened to load the kernel (and hence
there is no copy); this case doesn't require new configuration
information, it just re-uses the existing ${loadaddr} value.

The entry point also always comes from the image header; with similar
absolute/sdram-relative/image-relative derivations depending on patch-set.

I don't see any requirement for new configuration information here.

-- 
nvpublic