+++ /dev/null
-##########################################################################################\r
-!!!!!!!!!!!!!!!!! Notes for this ChangeLog.txt !!!!!!!!!!!!!!!!!\r
-\r
-This log file is used to record two kinds of important information:\r
- a) "Non-Compatible Changes": all non-compatible changes should be recorded. These info\r
- will help the package user to merge this package; and some non-compatible changes\r
- can also be added into release notes as news features when we release this package.\r
- Normally Non-Compatible Changes contains the following types:\r
- 1) Package's external services were changed/updated\r
- 2) Package's common .h file is renamed, deleted, or the file path is changed.\r
- 3) The definition of package's common data structure is changed\r
- ...\r
-\r
- b) "Important Compatible Changes": some important compatible changes can aslo be recorded\r
- in this file, and we can add these updating into release notes when we release this\r
- package.\r
-\r
-Non-Compatible and Compatible example format:\r
-==========================================================================================\r
-EDK_0010: Non-Compatible: owner\r
-\r
- Class_HFile: PPI A of MdePkg has been removed.\r
-\r
- Code Change :\r
- 1) Removed the .h file: MdePkg\Include\Ppi\A.h\r
-\r
- Possible Impacts:\r
- 1) All modules that used this PPI A should be updated.\r
-\r
-==========================================================================================\r
-EDK_0000: Compatible: owner\r
-\r
- Class_BuildTool: with the EDK_0000 build.exe, the build performance is enhanced great.\r
-\r
- Code Change :\r
- 1) BaseTools\Bin\Win32\build.exe\r
-\r
-!!!!!!!!!!!!!!!!!! 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
- Class_UefiEnable[0]: Uefi feature -Add component name 2 protocol support for\r
- all drivers that support component name protocol\r
- \r
-\r
- Code Change :\r
- 1) Update MdeModulePkg/Bus/Pci/*\r
- 2) Update MdeModulePkg/Bus/Scsi/*\r
- 3) Update MdeModulePkg/Bus/Usb/*\r
- 4) Update MdeModulePkg/Universal/Disk/*\r
- 5) Update MdeModulePkg/Universal/DebugPortDxe/*\r
- 6) Update MdeModulePkg/Universal/Console/*\r
- 7) Update MdeModulePkg/Universal/Network/*\r
- \r
- possible impact:\r
- 1) To produce the component name 2 protocol, platform DSC file needs to set feature\r
- flag 'PcdComponentName2Disable' to 'FALSE'\r
-\r
-==========================================================================================\r
-EDK_3967: Non-Compatible: lgao4\r
-\r
- Class_Library: Remove PeCoffLoader library class and its instances.\r
-\r
- Code Change :\r
- 1) Remove MdeModulePkg/Include/Library/PeCoffLoaderLib.h\r
- 2) Remove MdeModulePkg/Library/DxePeCoffLoaderFromHobLib and PeiDxePeCoffLoaderLib instance\r
- 3) Modify PeiCore, DxeIpl and DxeCore to use PeCoffLib in place of PeCoffLoaderLib.\r
-\r
- Possible Impacts:\r
- 1) All modules don't use PeCoffloader library class any longer to load PeImage. \r
- If necessary, they should use PeCoffLib of MdePkg to load PeImage.\r
-\r
-==========================================================================================\r
-EDK_3931: Non-Compatible: klu2\r
- \r
- Class_PIEnable[5]: New library class for S3Resume and Recovery for DxeIpl PEIM.\r
- \r
- Code Change:\r
- 1) Add new library class \r
- a) MdeModulePkg/Include/Library/S3Lib.h\r
- b) MdeModulePkg/Include/Library/RecoveryLib.h\r
- 2) Add NULL library instances for MdeModulePkg:\r
- a) MdeModulePkg/Library/PeiS3LibNull/PeiS3LibNull.inf.\r
- b) MdeModulePkg/Library/PeiRecoveryLibNull/PeiRecoveryLibNull.inf\r
- 3) Add framework implement library instances:\r
- a) IntelFrameworkModulePkg/Library/PeiS3Lib/PeiS3Lib.inf\r
- b) IntelFrameworkModulePkg/Library/PeiRecovery/PeiRecovery.inf\r
- \r
- Possible Impacts:\r
- 1) In DSC file, real platform should select:\r
- S3Lib library class -> IntelFrameworkModulePkg/Library/PeiS3Lib/PeiS3Lib.inf\r
- RecoveryLib library class -> IntelFrameworkModulePkg/Library/PeiRecovery/PeiRecovery.inf\r
- \r
- Nt32 platform should select:\r
- S3Lib library class -> MdeModulePkg/Library/PeiS3LibNull/PeiS3LibNull.inf.\r
- RecoveryLib library class -> MdeModulePkg/Library/PeiRecoveryLibNull/PeiRecoveryLibNull.inf\r
- \r
-==========================================================================================\r
-EDK_3922: Non-Compatible: qwang12, klu2\r
- Class_PIEnable[2]: Update PEI core to only consume EFI_PEI_FIRMWARE_VOLUME_INFO_PPI\r
-\r
- Code Change :\r
- 1) Update PEI core to consume EFI_PEI_FIRMWARE_VOLUME_INFO_PPI to get the location of new FVs other than BFV\r
- reported by PEIMs . \r
-\r
- Possible Impacts:\r
- 1) Platform code that is going to inform PEI core about the new FVs other than BFV should install \r
- EFI_PEI_FIRMWARE_VOLUME_INFO_PPI. A library function named PeiPiLibBuildPiFvInfoPpi() defined in \r
- MdePkg\Include\Library\PeiPiLib.h can be used to install the PPI. \r
- There are two notes worth mentioning:\r
- 1) Platform PEIMs should report at least FVs containing DXE_CORE and all other PEIM to PEI Core if they\r
- are not in the BFV. \r
- 2) PEI core will dispatch PEIMs in the FV reported by PeiPiLibBuildPiFvInfoPpi() and invoke BuildFvHob () to build the \r
- FV HOB for this FV (see Section 4.8.1.2 of Vol 1 named Multiple Firmware Volume Support for details). \r
- If PEIM only want to inform DXE core about the existance of the new FV, it should call BuildFvHob instead.\r
- \r
- \r
- Class_PIEnable[3]: Update PEI core to support RegisterForShadow feature introduced by PI spec\r
-\r
- Code Change :\r
- 1) DXEIPL no longer produce EFI_PEI_FV_FILE_LOADER_PPI defined in Framework PEI CIS.\r
-\r
- Possible Impacts:\r
-\r
- 1)All PEIMs that need to shadow itself into memory and rerun the entry point should be updated to call RegisterForShadow\r
- (PeiServicesLibRegisterForShadow () is a helper function).\r
- 2)The depex of PEIMs that including EFI_PEI_FV_FILE_LOADER_PPI (or gEfiPeiFvFileLoaderPpiGuid) should be removed.\r
- \r
-\r
- Class_PIEnable[4]: Update PEI core to produce other new features defined in PI spec\r
-\r
- Code Change :\r
- 1) Add the following services: FfsGetFileInfo, FfsFindFileByName and FfsGetVolumeInfo\r
-\r
- Possible Impacts:\r
-\r
- 1) Platform code is recommended to make use of these new PI features. The functions in MdePkg/Include/Library/PeiServicesLib.h are \r
- recommended as PeiServices is saved for every PEI Services API invokation.\r
-\r
-==========================================================================================\r
-EDK_3871: Non-Compatible: klu2\r
- \r
- Class_PIEnable[1]: Use new entry point for PeiCore defined in PI specification.\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 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
- 1) Platform should select MdePkg/Library/PeiCoreEntryPoint/PeiCoreEntryPoint.inf for \r
- PeiMain module.\r
- 2) The SecCore module should provide parameters for new entry point defined in \r
- MdePkg\Include\Library\PeiCoreEntryPoint.h\r
- \r
-==========================================================================================\r
-EDK_3866: Compatible: qhuang8\r
-\r
- Class_UefiEnable[0]: Uefi2.1 feature - Add Hardware Error Record Persistence Support \r
- Code Change :\r
- 1) Modify MdeModulePkg/Universal/Variable/RuntimeDxe\r
- 2) Modify MdeModulePkg/Universal/Variable/EmuRuntimeDxe\r
-\r
-==========================================================================================\r
-EDK_3773: Non-Compatible: qwang12\r
-\r
- Class_PIEnable[0]: Enable DXE Core to produce EFI_FIRMWARE_VOLUME2_PROTOCOL only.\r
-\r
- Code Change :\r
- 1) Modify MdeModulePkg/Core/Dxe/DxeMain.inf module to produce only\r
- EFI_FIRMWARE_VOLUME2_PROTOCOL. Previously, EFI_FIRMWARE_VOLUME_PROTOCOL\r
- is produced by Dxe Core.\r
-\r
- Possible Impacts:\r
- 1) All modules that references EFI_FIRMWARE_VOLUME_PROTOCOL must be updated to use\r
- EFI_FIRMWARE_VOLUME2_PROTOCOL.\r
- 2) All modules that references gEfiFirmwareVolumeProtocolGuid must be updated to\r
- use gEfiFirmwareVolume2ProtocolGuid.\r
- 3) The gEfiFirmwareVolumeProtocolGuid in [Depex] section of INF file should updated.\r
- And the package dependency should also be changed if needed due to this protocol\r
- GUID change.\r