!!!!!!!!!!!!!!!!!! End of Notes !!!!!!!!!!!!!!!!!!\r
##########################################################################################\r
\r
+==========================================================================================\r
+EDK_4310: Non-Compatible: qhuang8\r
+ Class_ModuleRemove[0]: Remove AtapiPassThru module from MdeModulePkg. AtapiPassThru\r
+ module is only used for testing. We already have a driver in OptionRomPkg to\r
+ produce ScsiPassThru and ExtScsiPassThru based on PCD setting. We can remove it\r
+ from MdeModulePkg.\r
+\r
+ Code Change :\r
+ 1) Remove module MdeModulePkg/Bus/Pci/AtapiPassThruDxe/AtapiPassThru.inf \r
+\r
+ Impact to platform code:\r
+ If a platform happens to refer to this module in their dsc file, please use the\r
+ counterpart module in OptionRomPkg.\r
+\r
+==========================================================================================\r
+EDK_4067: Non-Compatible: qwang12\r
+ Class_PIEnable[6]: PEI core does not build FV HOB upon notification of a EFI_PEI_FIRMWARE_VOLUME_INFO_PPI automatically.\r
+\r
+ Code Change :\r
+ 1) MdeModulePkg/Core/Pei/FwVol/FwVol.c \r
+ \r
+ Impact to platform code:\r
+ 1) If platform module want to inform both PEI core and DXE core about the existance of new FV \r
+ it must both install EFI_PEI_FIRMWARE_VOLUME_INFO_PPI and FV HOB. \r
+\r
+ A example is given belows:\r
+ \r
+ PiLibInstallFvInfoPpi (\r
+ NULL,\r
+ Buffer,\r
+ (UINT32) FvHeader->FvLength,\r
+ NULL,\r
+ NULL\r
+ );\r
+ \r
+ BuildFvHob (\r
+ (EFI_PHYSICAL_ADDRESS) (UINTN) Buffer,\r
+ (UINT32) FvHeader->FvLength\r
+ );\r
+\r
+ PEI core does not automatically build FV HOB upon notification of a EFI_PEI_FIRMWARE_VOLUME_INFO_PPI. \r
+ The description in Item 2 in Section 4.8.1.2 in Vol 1 of PI spec will be updated to remove the \r
+ "Create a new firmware volume HOB" wording.\r
+ \r
+\r
==========================================================================================\r
EDK_4000-4006: Compatible: qhuang8\r
\r
\r
Code Change:\r
1) PeiMain module use PeiCoreEntryPoint library class but *not* original OldPeiCoreEntryPoint.\r
- 2) The memory service in PeiMain module get CAR base and size from parameter of PeiCore's\r
+ 2) The memory service in PeiMain module get temporary memory base and size from parameter of PeiCore's\r
Entry point directly but *not* computed from stack's base.\r
\r
Possible Impacts:\r