On June 13, 2025 thus sayeth Yannic Moog: > 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. > > Here is an example build output of a phycore-imx8mp: > > BINMAN .binman_stamp > Image 'image' is missing optional external blobs but is still functional: > tee-os > > /binman/section/fit/images/tee/tee-os (tee.bin): > See the documentation for your board. You may need to build Open Portable > Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin > > Image 'image' has faked optional external blobs and is still functional: > tee.bin > > OFCHK .config > > The output stays to inform/warn the user, but in this case the tee-os > entry will not be present in the final image. > > --- > Changes in v3: > - Fix all failing tests > - add commit that reworks bin.elf test > - add section data to failing tests. E.g. tee-os contains missing > tee.bin, but is still included in the image. > - remove _entries -> GetEntries() refactor patch > - reorder commits -> smaller fixes before refactor EDITME: use bulletpoints > and terse descriptions. > - squash commits so that for each commits all binman tests should pass now > - rebase on next > - Link to v2: > https://lore.kernel.org/r/20250527-binman_faked_optional-v2-0-3362ab897...@phytec.de >
Reviewed-by: Bryan Brattlof <b...@ti.com> Thanks for fixing this. That error message has been on my todo list for a while as well :) ~Bryan
signature.asc
Description: PGP signature