[PATCH v3 0/4] mkimage: validate image references in FIT configurations
Tom Rini
trini at konsulko.com
Fri Jun 6 00:57:21 CEST 2025
On Wed, May 21, 2025 at 06:27:41AM +0000, Aristo Chen wrote:
> Hi all,
>
> I would like to apologize for the confusion caused by my v2 submission. Due
> to an issue in how I sent the patches, the series did not appear correctly
> grouped on Patchwork, making it harder to follow and review.
>
> This series introduces a validation step in mkimage to ensure that all image
> names referenced under the /configurations node of a FIT source (ITS) are
> actually defined under the /images node.
>
> ### Motivation
>
> When using mkimage to build FIT images, it's easy to mistakenly reference
> nonexistent image nodes in configurations (e.g., referencing a missing `fdt` or
> `firmware` node). Such issues are often not caught until runtime in U-Boot.
>
> This series aims to catch these errors early during FIT image creation by
> validating the configuration references in mkimage itself.
This seems to introduce problems on a number of platforms such as
evb-rk3288 and so it might be worthwhile to run v4 through CI before
posting, thanks.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20250605/9a68c8fd/attachment.sig>
More information about the U-Boot
mailing list