[PATCH v4 0/6] Improve FIT signature handling

[Tom Rini]

On Wed, May 13, 2026 at 04:08:10PM +0200, Ludwig Nussel wrote:
> This patch series tries to improve dealing with FIT
> (configuration-)signatures a bit:
>   - make signatures work with QEMU. QEMU brings it's own device tree at
>     a memory address. U-Boot expects public keys in it's own DT though.
>     So merge both.
>   - (optionally) enforce signatures so we can't accidentally boot
>     unsigned fit images. Quite an easy oversight, esp when qemu
>     previously didn't even use the built in DT.
>   - make iminfo verify configuration signatures, not just image hashes
> 
> The tests were created with the help of copilot and manual fixups. I
> have to admit that the log output of those tests is not something I can
> grok. I've left the tags copilot added in the commits even though
> checkpatch complains. Not sure what the policy is.

Well, part of the policy currently is following:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-assistants.rst

But as Simon asked (so answer there instead please) what output is hard
to follow exactly?

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20260515/1a5fe804/attachment.sig>