[U-Boot] mkimage and load addresses beyond 4 Gb
At present, the load address and entry point are both unsigned int. I'm porting to aarch64, and will run the SPL at 0x803100. mkimage truncates this to 0x3100. Are there any plans to support a load address and entry point larger than 32 bits? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] mkimage and load addresses beyond 4 Gb
Dear John, In message CANaRHtnjB-eU=au7VWzBVnM=ERrvWhF7nKUzZUC4QfsJJaNF=a...@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 0x803100. mkimage truncates this to 0x3100. 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. 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: w...@denx.de Far back in the mists of ancient time, in the great and glorious days of the former Galactic Empire, life was wild, rich and largely tax free. - Douglas Adams, _The Hitchhiker's Guide to the Galaxy_ ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] mkimage and load addresses beyond 4 Gb
Hi, On 4 November 2014 12:55, Wolfgang Denk w...@denx.de wrote: Dear John, In message CANaRHtnjB-eU=au7VWzBVnM=ERrvWhF7nKUzZUC4QfsJJaNF=a...@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 0x803100. mkimage truncates this to 0x3100. 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 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
