From 53f495b9f0d03e6cf976329cff698e8fceaa4d8b Mon Sep 17 00:00:00 2001 From: Sunil V L Date: Fri, 8 Nov 2024 11:17:27 +0530 Subject: [PATCH] Refine URT_040 requirement (ARC #201) URT_040 merely states that non-volatile UEFI variables must be persistent across reboots. This is redundant statement and the requirement is not very clear. The intention of the requirement is to mandate non-volatile UEFI variables. So, just make it is clear that UEFI variables must be persistent. Fixes: https://github.com/riscv-non-isa/riscv-brs/issues/201 Signed-off-by: Sunil V L --- uefi.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uefi.adoc b/uefi.adoc index eaaf5fc..f893fdd 100644 --- a/uefi.adoc +++ b/uefi.adoc @@ -79,7 +79,7 @@ See additional <>. * `GetTime()` and `SetTime()` MUST be appropriately described in the `EFI_RT_PROPERTIES_TABLE`. | `URT_030` a| The UEFI `ResetSystem()` runtime service MUST be implemented. 2+| _The OS MUST call the `ResetSystem()` runtime service call to reset or shutdown the system, preferring this to SBI, ACPI or other system-specific mechanisms. This allows for systems to perform any required system tasks on the way out (e.g. servicing `UpdateCapsule()` or persisting non-volatile variables in some systems)._ -| `URT_040` | Non-volatile UEFI variables MUST persist across calls to the `ResetSystem()` runtime service call. +| `URT_040` | The UEFI variables MUST persist across calls to the `ResetSystem()` runtime service call. | `URT_050` | UEFI runtime services MUST be able to update the UEFI variables directly without the aid of an OS. 2+| _UEFI variables are normally saved in a dedicated storage which is not directly accessible by the operating system._ | `URT_060` a| The following requirements MUST be met for systems with UEFI secure boot: