Stephen Warren wrote at Friday, September 30, 2011 1:53 PM: > 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.
Wolfgang, does this change look like a reasonable approach? > 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. What are your thoughts on the legacy format; should we ignore it? We could probably steal some bit in one of the fields for this flag, although technically that would be a change to the format, with potential compatibility issues. Thanks. -- nvpublic _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
