- Variable Architectural Protocol as defined in the DXE CIS\r
-\r
- This code is used to produce the UEFI 2.0 runtime variable services\r
-\r
- The GetVariable (), GetNextVariableName (), and SetVariable () UEFI 2.0 \r
- services are added to the EFI system table and the \r
- EFI_VARIABLE_ARCH_PROTOCOL_GUID protocol is registered with a NULL pointer.\r
-\r
- No CRC of the EFI system table is required, as it is done in the DXE core.\r
-\r
- Copyright (c) 2006, Intel Corporation \r
- All rights reserved. This program and the accompanying materials \r
+ Variable Architectural Protocol as defined in PI Specification VOLUME 2 DXE\r
+\r
+ This provides the services required to get and set environment variables. This \r
+ protocol must be produced by a runtime DXE driver and may be consumed only by \r
+ the DXE Foundation. The DXE driver that produces this protocol must be a runtime \r
+ driver. This driver is responsible for initializing the GetVariable(), \r
+ GetNextVariableName(), and SetVariable() fields of the UEFI Runtime Services Table.\r
+\r
+ After the three fields of the UEFI Runtime Services Table have been initialized, \r
+ the driver must install the EFI_VARIABLE_ARCH_PROTOCOL_GUID on a new handle with \r
+ a NULL interface pointer. The installation of this protocol informs the DXE Foundation \r
+ that the read-only and the volatile environment variable related services are \r
+ now available and that the DXE Foundation must update the 32-bit CRC of the UEFI \r
+ Runtime Services Table. The full complement of environment variable services are \r
+ not available until both this protocol and EFI_VARIABLE_WRITE_ARCH_PROTOCOL are \r
+ installed. DXE drivers that require read-only access or read/write access to volatile \r
+ environment variables must have this architectural protocol in their dependency \r
+ expressions. DXE drivers that require write access to nonvolatile environment \r
+ variables must have the EFI_VARIABLE_WRITE_ARCH_PROTOCOL in their dependency \r
+ expressions.\r
+\r
+ Copyright (c) 2006 - 2008, Intel Corporation. All rights reserved.<BR>\r
+ This program and the accompanying materials \r