On Fri, 13 Jun 2025 14:02:39 +0200, Yannic Moog wrote:
> This series solves a contradiction regarding ext blobs packaged in
> binman. When they are marked as optional, by default they are faked, two
> messages are emitted. One says the image is not functional the other
> says the image is still functional. Both concern the same binman
> entry/blob.
>
> Binman is set up to have fake external blobs in case they are missing.
> This is regardless on whether they are optional or not.
> The implementation does not allow different types of entries to override
> the faking decision; at least there wouldn't be much sense in doing so.
>
> [...]
Applied to u-boot/next, thanks!
[1/6] binman: drop "faked" return value from check_fake_fname
commit: a657d87f08789c4c50423897bd5ee052c6223ee6
[2/6] binman: mark optional missing blobs as absent
commit: 3ae668b9d2101d111d257ee7d8912c19cfb0e102
[3/6] binman: rework dropping absent entries from packaged image
commit: 21bc3433a43d3add3430543c9eee2a95d4dee2f6
[4/6] binman: add faked optional entry case in CheckForProblems
commit: f5817e05efd39dd455c2e6a0f0622d709fe7ea2d
[5/6] binman: ftest: pass allow_fake_blob to _DoReadFileDtb
commit: e749d64b4622806072c56a839cf9a36a5081b575
[6/6] binman: test: assert optional blobs don't cause non-functionality
commit: 0dbb0a8d1f2aefb2a7fdd8e627edd955e4fe8d3a
--
Tom
