[U-Boot] [PATCH 1/2] image: Support relative-addresses property in FIT images

[Wolfgang Denk]

Dear Stephen Warren,

In message <1317412383-7731-1-git-send-email-swarren at nvidia.com> you 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, augment the FIT image
> syntax with a "relative-addresses" property, which indicates that the "load"
> and "entry" properties are an offset from SDRAM, rather than an absolute
> address.
> 
> In theory, a similar change could be made to the legacy uImage format.
> However, representing the a "relative-addresses" flag in that format is
> problematic, so I have ignored that possibility for now.
...
> +  - relative-addresses : Indicates the the values of the load and entry
> +    properties are to be interpreted as relative to the base of SDRAM, rather
> +    than as an absolute values.

How is "base of SDRAM" defined, for example in the case of several
non-contiguously mapped banks of RAM?

Please add this to the comment.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Q:  What's a light-year?
A:  One-third less calories than a regular year.