<ProtocolCName>gEfiFirmwareVolumeBlockProtocolGuid</ProtocolCName>\r
</Protocol>\r
</Protocols>\r
+ <Hobs>\r
+ <HobTypes HobGuidCName="gEfiFlashMapHobGuid" Usage="ALWAYS_CONSUMED">\r
+ <HobType>GUID_EXTENSION</HobType>\r
+ </HobTypes>\r
+ </Hobs>\r
<PPIs>\r
<Ppi Usage="ALWAYS_PRODUCED">\r
<PpiCName>gPeiFlashMapPpiGuid</PpiCName>\r
</Ppi>\r
</PPIs>\r
<Guids>\r
- <GuidCNames Usage="ALWAYS_CONSUMED">\r
- <GuidCName>gEfiFlashMapHobGuid</GuidCName>\r
- </GuidCNames>\r
<GuidCNames Usage="ALWAYS_CONSUMED">\r
<GuidCName>gEfiFirmwareFileSystemGuid</GuidCName>\r
</GuidCNames>\r
<PcdEntry PcdItemType="DYNAMIC">\r
<C_Name>PcdFlashNvStorageVariableBase</C_Name>\r
<TokenSpaceGuidCName>gEfiGenericPlatformTokenSpaceGuid</TokenSpaceGuidCName>\r
- <HelpText>The driver sets the NV Storage FV base address defined by this PCD. \r
+ <HelpText>The driver sets the NV Storage FV base address defined by this PCD.\r
This base address point to an EFI_FIRMWARE_VOLUMN_HEADER struct. Variable PEIM\r
will get the base address from this PCD. In NT emulator, this PCD is a DYNAMIC\r
- type, as FD is mapped to process space by WinNT OS. On real platform, it is \r
+ type, as FD is mapped to process space by WinNT OS. On real platform, it is\r
normally a FIXED_AT_BUILD type as system memory map is fixed to BIOS.</HelpText>\r
</PcdEntry>\r
<PcdEntry PcdItemType="DYNAMIC">\r