Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require FMP and "on disk" OsIndicationsSupported bits when supported #137

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

vstehle
Copy link
Collaborator

@vstehle vstehle commented Jan 14, 2025

  • We are requiring the OsIndicationsSupported Variable.
  • When in-band firmware update are supported, we are requiring support for FMP and "on disk".
    Therefore, let's require the corresponding OsIndicationsSupported bits as well.

In this series there is also a commit to add a new section anchor and a commit to clarify our mention of the FMP format, which could probably be merged immediately.

Add an anchor to be able to refer to the "In-band firmware update" section.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>
We require in-band firmware updates in the "Firmware Management Protocol
Data Capsule Structure" format. This is a bit misleading as this format
described in UEFI § 23.3.2 is only about the capsule body.

Refer to the Firmware Management Protocol format instead to avoid the
confusion, remove the unnecessary quotation marks and introduce the FMP
acronym.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>
Require to set the FMP and "on disk" OsIndicationsSupported bits when
in-band firmware update is supported.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>
@@ -622,8 +622,8 @@ In-band firmware update

If firmware update is performed in-band (firmware on the application processor
updates itself), then the firmware shall implement the `UpdateCapsule()` runtime
service and accept only authenticated updates in the "Firmware Management
Protocol Data Capsule Structure" format as described in :UEFI:`23.3`, with
service and accept only authenticated updates in the Firmware Management
Copy link
Contributor

@xypron xypron Jan 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UpdateCapsule() expects a scatter list. From that scatter list a capsule can be reconstructed as described in "23.3.2 DEFINED FIRMWARE MANAGEMENT PROTOCOL DATA CAPSULE STRUCTURE". The capsule consists of a EFI_FIRMWARE_MANAGEMENT_CAPSULE_IMAGE_HEADER and a capsule body. The body starts with an EFI_FIRMWARE_MANAGEMENT_CAPSULE_HEADER.

The term "Firmware Management Protocol Format" would not catch the existence of a scatter list and an EFI_FIRMWARE_MANAGEMENT_CAPSULE_IMAGE_HEADER.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants