X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=MdeModulePkg%2FChangeLog.txt;h=5ff6510cfc3ab50ec225a69a4d43f02cc157e84e;hb=f9f937d243c8c9615119be2f2b35821e7de80925;hp=5b8eabcba8d236eb4d2f161200fae7cb000edd07;hpb=b4f5f5d69cc824af23bd094c204d319cfe020885;p=mirror_edk2.git diff --git a/MdeModulePkg/ChangeLog.txt b/MdeModulePkg/ChangeLog.txt index 5b8eabcba8..5ff6510cfc 100644 --- a/MdeModulePkg/ChangeLog.txt +++ b/MdeModulePkg/ChangeLog.txt @@ -38,44 +38,110 @@ EDK_0000: Compatible: owner !!!!!!!!!!!!!!!!!! End of Notes !!!!!!!!!!!!!!!!!! ########################################################################################## +========================================================================================== +EDK_4310: Non-Compatible: qhuang8 + Class_ModuleRemove[0]: Remove AtapiPassThru module from MdeModulePkg. AtapiPassThru + module is only used for testing. We already have a driver in OptionRomPkg to + produce ScsiPassThru and ExtScsiPassThru based on PCD setting. We can remove it + from MdeModulePkg. + Code Change : + 1) Remove module MdeModulePkg/Bus/Pci/AtapiPassThruDxe/AtapiPassThru.inf + Impact to platform code: + If a platform happens to refer to this module in their dsc file, please use the + counterpart module in OptionRomPkg. ========================================================================================== -EDK_3773: Non-Compatible: qwang12 +EDK_4067: Non-Compatible: qwang12 + Class_PIEnable[6]: PEI core does not build FV HOB upon notification of a EFI_PEI_FIRMWARE_VOLUME_INFO_PPI automatically. - Class_PIEnable[0]: Enable DXE Core to produce EFI_FIRMWARE_VOLUME2_PROTOCOL only. + Code Change : + 1) MdeModulePkg/Core/Pei/FwVol/FwVol.c + + Impact to platform code: + 1) If platform module want to inform both PEI core and DXE core about the existance of new FV + it must both install EFI_PEI_FIRMWARE_VOLUME_INFO_PPI and FV HOB. + + A example is given belows: + + PiLibInstallFvInfoPpi ( + NULL, + Buffer, + (UINT32) FvHeader->FvLength, + NULL, + NULL + ); + + BuildFvHob ( + (EFI_PHYSICAL_ADDRESS) (UINTN) Buffer, + (UINT32) FvHeader->FvLength + ); + + PEI core does not automatically build FV HOB upon notification of a EFI_PEI_FIRMWARE_VOLUME_INFO_PPI. + The description in Item 2 in Section 4.8.1.2 in Vol 1 of PI spec will be updated to remove the + "Create a new firmware volume HOB" wording. + + +========================================================================================== +EDK_4000-4006: Compatible: qhuang8 + + Class_UefiEnable[0]: Uefi feature -Add component name 2 protocol support for + all drivers that support component name protocol + + + Code Change : + 1) Update MdeModulePkg/Bus/Pci/* + 2) Update MdeModulePkg/Bus/Scsi/* + 3) Update MdeModulePkg/Bus/Usb/* + 4) Update MdeModulePkg/Universal/Disk/* + 5) Update MdeModulePkg/Universal/DebugPortDxe/* + 6) Update MdeModulePkg/Universal/Console/* + 7) Update MdeModulePkg/Universal/Network/* + + possible impact: + 1) To produce the component name 2 protocol, platform DSC file needs to set feature + flag 'PcdComponentName2Disable' to 'FALSE' + +========================================================================================== +EDK_3967: Non-Compatible: lgao4 + + Class_Library: Remove PeCoffLoader library class and its instances. Code Change : - 1) Modify MdeModulePkg/Core/Dxe/DxeMain.inf module to produce only - EFI_FIRMWARE_VOLUME2_PROTOCOL. Previously, EFI_FIRMWARE_VOLUME_PROTOCOL - is produced by Dxe Core. + 1) Remove MdeModulePkg/Include/Library/PeCoffLoaderLib.h + 2) Remove MdeModulePkg/Library/DxePeCoffLoaderFromHobLib and PeiDxePeCoffLoaderLib instance + 3) Modify PeiCore, DxeIpl and DxeCore to use PeCoffLib in place of PeCoffLoaderLib. Possible Impacts: - 1) All modules that references EFI_FIRMWARE_VOLUME_PROTOCOL must be updated to use - EFI_FIRMWARE_VOLUME2_PROTOCOL. - 2) All modules that references gEfiFirmwareVolumeProtocolGuid must be updated to - use gEfiFirmwareVolume2ProtocolGuid. - 3) The gEfiFirmwareVolumeProtocolGuid in [Depex] section of INF file should updated. - And the package dependency should also be changed if needed due to this protocol - GUID change. + 1) All modules don't use PeCoffloader library class any longer to load PeImage. + If necessary, they should use PeCoffLib of MdePkg to load PeImage. ========================================================================================== -EDK_3871: Non-Compatible: klu2 +EDK_3931: Non-Compatible: klu2 - Class_PIEnable[1]: Use new entry point for PeiCore defined in PI specification. + Class_PIEnable[5]: New library class for S3Resume and Recovery for DxeIpl PEIM. Code Change: - 1) PeiMain module use PeiCoreEntryPoint library class but *not* original OldPeiCoreEntryPoint. - 2) The memory service in PeiMain module get CAR base and size from parameter of PeiCore's - Entry point directly but *not* computed from stack's base. + 1) Add new library class + a) MdeModulePkg/Include/Library/S3Lib.h + b) MdeModulePkg/Include/Library/RecoveryLib.h + 2) Add NULL library instances for MdeModulePkg: + a) MdeModulePkg/Library/PeiS3LibNull/PeiS3LibNull.inf. + b) MdeModulePkg/Library/PeiRecoveryLibNull/PeiRecoveryLibNull.inf + 3) Add framework implement library instances: + a) IntelFrameworkModulePkg/Library/PeiS3Lib/PeiS3Lib.inf + b) IntelFrameworkModulePkg/Library/PeiRecovery/PeiRecovery.inf Possible Impacts: - 1) Platform should select MdePkg/Library/PeiCoreEntryPoint/PeiCoreEntryPoint.inf for - PeiMain module. - 2) The SecCore module should provide parameters for new entry point defined in - MdePkg\Include\Library\PeiCoreEntryPoint.h - + 1) In DSC file, real platform should select: + S3Lib library class -> IntelFrameworkModulePkg/Library/PeiS3Lib/PeiS3Lib.inf + RecoveryLib library class -> IntelFrameworkModulePkg/Library/PeiRecovery/PeiRecovery.inf + + Nt32 platform should select: + S3Lib library class -> MdeModulePkg/Library/PeiS3LibNull/PeiS3LibNull.inf. + RecoveryLib library class -> MdeModulePkg/Library/PeiRecoveryLibNull/PeiRecoveryLibNull.inf + ========================================================================================== EDK_3922: Non-Compatible: qwang12, klu2 Class_PIEnable[2]: Update PEI core to only consume EFI_PEI_FIRMWARE_VOLUME_INFO_PPI @@ -118,6 +184,21 @@ EDK_3922: Non-Compatible: qwang12, klu2 1) Platform code is recommended to make use of these new PI features. The functions in MdePkg/Include/Library/PeiServicesLib.h are recommended as PeiServices is saved for every PEI Services API invokation. +========================================================================================== +EDK_3871: Non-Compatible: klu2 + + Class_PIEnable[1]: Use new entry point for PeiCore defined in PI specification. + + Code Change: + 1) PeiMain module use PeiCoreEntryPoint library class but *not* original OldPeiCoreEntryPoint. + 2) The memory service in PeiMain module get temporary memory base and size from parameter of PeiCore's + Entry point directly but *not* computed from stack's base. + + Possible Impacts: + 1) Platform should select MdePkg/Library/PeiCoreEntryPoint/PeiCoreEntryPoint.inf for + PeiMain module. + 2) The SecCore module should provide parameters for new entry point defined in + MdePkg\Include\Library\PeiCoreEntryPoint.h ========================================================================================== EDK_3866: Compatible: qhuang8 @@ -126,3 +207,22 @@ EDK_3866: Compatible: qhuang8 Code Change : 1) Modify MdeModulePkg/Universal/Variable/RuntimeDxe 2) Modify MdeModulePkg/Universal/Variable/EmuRuntimeDxe + +========================================================================================== +EDK_3773: Non-Compatible: qwang12 + + Class_PIEnable[0]: Enable DXE Core to produce EFI_FIRMWARE_VOLUME2_PROTOCOL only. + + Code Change : + 1) Modify MdeModulePkg/Core/Dxe/DxeMain.inf module to produce only + EFI_FIRMWARE_VOLUME2_PROTOCOL. Previously, EFI_FIRMWARE_VOLUME_PROTOCOL + is produced by Dxe Core. + + Possible Impacts: + 1) All modules that references EFI_FIRMWARE_VOLUME_PROTOCOL must be updated to use + EFI_FIRMWARE_VOLUME2_PROTOCOL. + 2) All modules that references gEfiFirmwareVolumeProtocolGuid must be updated to + use gEfiFirmwareVolume2ProtocolGuid. + 3) The gEfiFirmwareVolumeProtocolGuid in [Depex] section of INF file should updated. + And the package dependency should also be changed if needed due to this protocol + GUID change.