Re: [PATCH] FIT: Parse `load` and `entry` addresses.

2020-07-13 Thread Christian Mauderer
Hello Ahmad, thanks for the fast review. I'll make the suggested changes and post a V2 (most likely) tomorrow. Best regards Christian On 13/07/2020 15:36, Ahmad Fatoum wrote: > Hello Christian, > > On 7/13/20 2:03 PM, Christian Mauderer wrote: >> According to the U-Boot documentation for the F

Re: [PATCH] FIT: Parse `load` and `entry` addresses.

2020-07-13 Thread Ahmad Fatoum
Hello Christian, On 7/13/20 2:03 PM, Christian Mauderer wrote: > According to the U-Boot documentation for the FIT file format, the load > and entry have to be allways defined for a "kernel" or "standalone". > But Barebox ignored the parameters. That changes with this patch. > > For backward comp

[PATCH] FIT: Parse `load` and `entry` addresses.

2020-07-13 Thread Christian Mauderer
According to the U-Boot documentation for the FIT file format, the load and entry have to be allways defined for a "kernel" or "standalone". But Barebox ignored the parameters. That changes with this patch. For backward compatibility the default address is still used for images without `load` or `

Re: [RFC PATCH 0/4] Introduce global.bootm.root env var for booting via PARTUUID

2020-07-13 Thread Robert Karszniewicz
On 7/9/20 4:14 PM, Sascha Hauer wrote: On Tue, Jun 30, 2020 at 03:48:30PM +0200, Robert Karszniewicz wrote: This patch introduces a new env var which specifies which device is the rootfs device to be used in Linux, passed to Linux via bootargs, identified by the rootfs partition's PARTUUID. glo