BRS-I EFI Cfg Table Requirement for EFI_DTB_TABLE_GUID (#196)

#173

Signed-off-by: Andrei Warkentin <[email protected]>

brs_tests.adoc

@@ -65,11 +65,12 @@
 | ID#            ^| Algorithm
 | `ME_UEFI_010_010` | _FIXME_.
 | `ME_UEFI_020_010` | _FIXME_.
-| `ME_UEFI_030_010` | _FIXME .
-| `OE_UEFI_040_010` | _FIXME .
-| `OE_UEFI_050_010` | _FIXME .
-| `ME_UEFI_060_010` | _FIXME .
-| `ME_UEFI_070_010` | _FIXME .
+| `ME_UEFI_030_010` | _FIXME_.
+| `OE_UEFI_040_010` | _FIXME_.
+| `OE_UEFI_050_010` | _FIXME_.
+| `ME_UEFI_060_010` | _FIXME_.
+| `ME_UEFI_070_010` | _FIXME_.
+| `ME_UEFI_070_010` | _FIXME_.
 |===
 
 <<<

recipes.adoc

@@ -46,7 +46,7 @@ unexpected behavior in a generic OS must be configured by firmware as opt-in.
 [%header, cols="10,10,10,10,10,10"]
 |===
 | Profile | UEFI | ACPI | DT | SBI | SMBIOS
-| >= RVA20 | >= 2.10 | >= 6.6 | N/A | >= 2.0 | >= 3.7.0
+| >= RVA20 | >= 2.10 | >= 6.6 | optional, >= v0.3 | >= 2.0 | >= 3.7.0
 |===
 
 === BRS-B Recipe
@@ -67,4 +67,4 @@ custom distributions.
 | >= RVA20 | EBBR, >= 2.1.0 cite:[EBBR] | optional, >= 6.6 | optional, >= v0.3 | >= 2.0 | optional, >= 3.7.0
 |===
 
-Either of ACPI table or Device Tree must be supplied, but never both at the same time.
+Either ACPI or DT may be used to describe hardware to the OS, but never both at the same time.

uefi.adoc

@@ -28,6 +28,10 @@ IMPORTANT: All content in this section is optional and recommended for BRS-B.
 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` | 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._
+| `UEFI_080` | A Device Tree MUST only be exposed to the OS iff no actual hardware description is included in the DT.
+2+|_Such a "dummy" DT could be installed by firmware, as a UEFI configuration table entry of type `EFI_DTB_TABLE_GUID`, to provide necessary
+hand-off info to an OS, for example, to provide RAM disk information
+(e.g. via `/chosen/linux,initrd-start`)._
 |===
 
 === BRS-I Security Requirements