Skip to content

Commit

Permalink
Address some feedback from Ved: "Chapter 5 Some of the requirements a…
Browse files Browse the repository at this point in the history
…re missing the RFC2119 keywords to indicate whether they are mandatory or optional." (#163)

Signed-off-by: Andrei Warkentin <[email protected]>
  • Loading branch information
andreiw committed May 16, 2024
1 parent 21b1ab0 commit 3e9e6b5
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions uefi.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -14,19 +14,19 @@ IMPORTANT: All content in this section is optional and recommended for BRS-B.
[%header, cols="5,25"]
|===
| ID# ^| Requirement
| `UEFI_010` | Implement a 64-bit UEFI firmware.
| `UEFI_020` | Meet the 3rd Party UEFI Certificate Authority (CA) requirements on UEFI memory mitigations cite:[MSUefiCaRequirements].
| `UEFI_030` a| Meet BRS-I specific memory map requirements:
| `UEFI_010` | MUST implement a 64-bit UEFI firmware.
| `UEFI_020` | MUST meet the 3rd Party UEFI Certificate Authority (CA) requirements on UEFI memory mitigations cite:[MSUefiCaRequirements].
| `UEFI_030` a| MUST meet the following memory map requirements:

* The default memory space attribute MUST be `EFI_MEMORY_WB`.
* Enable address translation.
* The default memory space attribute is `EFI_MEMORY_WB`.
* Address translation is enabled.
* Only use `EfiRuntimeServicesData` memory type for describing any SMBIOS data structures.
| `UEFI_040` | An implementation MAY comply with the _UEFI Platform Initialization Specification_ cite:[UEFI-PI].
| `UEFI_050` | All hart manipulation internal to a firmware implementation SHOULD be done before completion of the `EFI_EVENT_GROUP_READY_TO_BOOT` event, with all secondary harts remaining offline from that point on.
2+| _This ensures an OS loader is entered with an OS-compatible state for all harts._
| `UEFI_060` | Declare the `EFI_CONFORMANCE_PROFILES_UEFI_SPEC_GUID` conformance profile.
| `UEFI_060` | The implementation MUST declare the `EFI_CONFORMANCE_PROFILES_UEFI_SPEC_GUID` conformance profile.
2+| _The `EFI_CONFORMANCE_PROFILES_UEFI_SPEC_GUID` conformance profile MUST be declared, as the BRS requirements are a superset of UEFI cite:[UEFI] (Section 2.6)._
| `UEFI_070` | Declare the `EFI_CONFORMANCE_PROFILE_BRS_1_0_SPEC_GUID` conformance profile `({ 0x05453310, 0x0545, 0x0545, { 0x05, 0x45, 0x33, 0x05, 0x45, 0x33, 0x05, 0x45 }})`.
| `UEFI_070` | The implementation MUST declare the `EFI_CONFORMANCE_PROFILE_BRS_1_0_SPEC_GUID` conformance profile `({ 0x05453310, 0x0545, 0x0545, { 0x05, 0x45, 0x33, 0x05, 0x45, 0x33, 0x05, 0x45 }})`.
2+| _Only a system fully compliant to the requirements in this section MAY declare the `EFI_CONFORMANCE_PROFILE_BRS_1_0_SPEC_GUID` conformance profile._
|===

Expand Down

0 comments on commit 3e9e6b5

Please sign in to comment.