Hi Simon,
On 5/14/25 9:44 PM, Simon Glass wrote:
Hi,
On Tue, 13 May 2025 at 17:28, Quentin Schulz <quentin.sch...@cherry.de> wrote:
Hi Aristo,
On 5/5/25 12:08 PM, Aristo Chen wrote:
When parsing a FIT image source (ITS), mkimage does not currently check
whether the image names referenced in the /configurations section (e.g.
"kernel", "fdt", "ramdisk", "loadables") actually exist in the /images
node.
This patch introduces a validation step during FIT import that iterates
over each configuration and verifies that all referenced image names are
defined under /images. If a missing image is detected, an appropriate
error is reported and mkimage exits with FDT_ERR_NOTFOUND.
One option (for boards which use Binman) would be to put these sorts
of checks in there, since it might be easier to code? But having it in
mkimage as well seems reasonable to me.
mkimage can be used to generate images from outside of U-Boot. I believe
this is what Yocto does for example to generate kernel FIT (see
UBOOT_MKIMAGE and others), so having an additional check in mkimage is
probably a good idea.
Cheers,
Quentin
Regards,
Simon
