diff options
author | Tom Rini <trini@konsulko.com> | 2025-06-26 09:54:24 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2025-06-26 09:54:24 -0600 |
commit | d4f61eae2ab768a0427794f20d07ac2826102d21 (patch) | |
tree | da5b4f3a68007a0b1e558b1f4385a8631ab2f91a /lib/linux_string.c | |
parent | 2cfbf412a0dc8d788d9bb2d8704ffa939b99e293 (diff) | |
parent | 0dbb0a8d1f2aefb2a7fdd8e627edd955e4fe8d3a (diff) |
Merge patch series "Fix handling of optional blobs in binman"
Yannic Moog <y.moog@phytec.de> says:
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.
Link: https://lore.kernel.org/r/20250613-binman_faked_optional-v3-0-1e23dd7c41a2@phytec.de
Diffstat (limited to 'lib/linux_string.c')
0 files changed, 0 insertions, 0 deletions