[U-Boot] mkimage and load addresses beyond 4 Gb
Simon Glass
sjg at chromium.org
Wed Nov 5 01:42:54 CET 2014
Hi,
On 4 November 2014 12:55, Wolfgang Denk <wd at denx.de> wrote:
>
> Dear John,
>
> In message <CANaRHtnjB-eU=au7VWzBVnM=ERrvWhF7nKUzZUC4QfsJJaNF=A at mail.gmail.com> you wrote:
> >
> > At present, the load address and entry point are both "unsigned int". I'm
> > porting to aarch64, and will run the SPL at 0x8031000000. mkimage
> > truncates this to 0x31000000. Are there any plans to support a load
> > address and entry point larger than 32 bits?
>
> The old legacy (binary) uImage header uses u32, and there is no
> compatible way to change that.
>
> I think for any 64 bit architecture you will want to use FIT images
> right from the beginning. This will also need some patches, though.
That sounds good. It seems silly to maintain legacy formats with new
architectures, FIT is much much more flexible (hashing, verified boot,
more image types, etc.)
To reduce friction we could perhaps enhance mkimage so it can
auto-generate a .its file for the common case.
Regards,
Simon
More information about the U-Boot
mailing list