gArmVirtTokenSpaceGuid = { 0x0B6F5CA7, 0x4F53, 0x445A, { 0xB7, 0x6E, 0x2E, 0x36, 0x5B, 0x80, 0x63, 0x66 } }\r
gEarlyPL011BaseAddressGuid = { 0xB199DEA9, 0xFD5C, 0x4A84, { 0x80, 0x82, 0x2F, 0x41, 0x70, 0x78, 0x03, 0x05 } }\r
\r
+[Protocols]\r
+ gFdtClientProtocolGuid = { 0xE11FACA0, 0x4710, 0x4C8E, { 0xA7, 0xA2, 0x01, 0xBA, 0xA2, 0x59, 0x1B, 0x4C } }\r
+\r
[PcdsFixedAtBuild, PcdsPatchableInModule]\r
#\r
# This is the physical address where the device tree is expected to be stored\r
#\r
gArmVirtTokenSpaceGuid.PcdDeviceTreeAllocationPadding|256|UINT32|0x00000002\r
\r
-[PcdsDynamic, PcdsFixedAtBuild]\r
#\r
- # ARM PSCI function invocations can be done either through hypervisor\r
- # calls (HVC) or secure monitor calls (SMC).\r
- # PcdArmPsciMethod == 1 : use HVC\r
- # PcdArmPsciMethod == 2 : use SMC\r
+ # Binary representation of the GUID that determines the terminal type. The\r
+ # size must be exactly 16 bytes. The default value corresponds to\r
+ # EFI_VT_100_GUID.\r
#\r
- gArmVirtTokenSpaceGuid.PcdArmPsciMethod|0|UINT32|0x00000003\r
-\r
- gArmVirtTokenSpaceGuid.PcdFwCfgSelectorAddress|0x0|UINT64|0x00000004\r
- gArmVirtTokenSpaceGuid.PcdFwCfgDataAddress|0x0|UINT64|0x00000005\r
+ gArmVirtTokenSpaceGuid.PcdTerminalTypeGuidBuffer|{0x65, 0x60, 0xA6, 0xDF, 0x19, 0xB4, 0xD3, 0x11, 0x9A, 0x2D, 0x00, 0x90, 0x27, 0x3F, 0xC1, 0x4D}|VOID*|0x00000007\r
\r
[PcdsFeatureFlag]\r
#\r
# The default is to turn off the kludge; DSC's can selectively enable it.\r
#\r
gArmVirtTokenSpaceGuid.PcdKludgeMapPciMmioAsCached|FALSE|BOOLEAN|0x00000006\r
+\r
+ #\r
+ # Pure ACPI boot\r
+ #\r
+ # Inhibit installation of the FDT as a configuration table if this feature\r
+ # PCD is TRUE. Otherwise, the OS is presented with both a DT and an ACPI\r
+ # description of the platform, and it is up to the OS to choose.\r
+ #\r
+ gArmVirtTokenSpaceGuid.PcdPureAcpiBoot|FALSE|BOOLEAN|0x0000000a\r