Right now the ESRT firmware resource entries never reflect a failed
update. LastAttemptStatus and LastAttemptVersion stay at whatever they
were set to at boot, so an OS querying ESRT after a rejected or failed
capsule has no way to see that anything went wrong.
This series threads last-attempt tracking through the RAW capsule
update path (raw image writes and the DFU-backed image writes it
shares code with), maps the internal error codes to UEFI status codes,
and makes sure the FMP variable gets updated on both success and
failure so ESRT stays accurate. It also fixes FW version extraction so
it still happens when authentication fails, since that path was
skipping the version read entirely and left ESRT with stale version
info on rejected capsules.
The last patch adds "efidebug capsule images", which prints the FMP
image descriptors a board currently exposes (index, name, type GUID).
This got more useful once fw_images[] started varying at runtime
depending on what a board actually has.
This work is part of multi-image capsule update support for
Qualcomm boards.
There is no dependency on any other series.
Balaji Selvanathan (4):
efi_loader: firmware: track last attempt status for ESRT reporting
efi_loader: firmware: add last attempt tracking for RAW capsules
efi_loader: Extract FW version even on authentication failure
efidebug: capsule: add a command to list updatable firmware images
---
Balaji Selvanathan (4):
efi_loader: firmware: track last attempt status for ESRT reporting
efi_loader: firmware: add last attempt tracking for RAW capsules
efi_loader: Extract FW version even on authentication failure
efidebug: capsule: add a command to list updatable firmware images
cmd/efidebug.c | 102 +++++++++++++++++
lib/efi_loader/efi_firmware.c | 121 ++++++++++++++++++---
.../test_efi_capsule/test_capsule_firmware_raw.py | 22 ++++
3 files changed, 232 insertions(+), 13 deletions(-)
---
base-commit: 36c377b9859ffb53eb1e39ea31e8d96d1e0fe1e5
change-id: 20260811-efi-esrt-last-attempt-62a10e7807f2
Best regards,
--
Balaji Selvanathan <[email protected]>
