remove member context from _EFI_MTFTP4_TOKEN structure.

[mirror_edk2.git] / MdeModulePkg / ChangeLog.txt

diff --git a/MdeModulePkg/ChangeLog.txt b/MdeModulePkg/ChangeLog.txt
index 324868ee1f41f69ca7ecb1d744fd17a913b68416..e50ab47366e7a2747bbdb6f0961bbd385b962294 100644 (file)
--- a/MdeModulePkg/ChangeLog.txt
+++ b/MdeModulePkg/ChangeLog.txt
@@ -38,6 +38,37 @@ EDK_0000: Compatible: owner
 !!!!!!!!!!!!!!!!!!                     End of Notes                     !!!!!!!!!!!!!!!!!!\r
 ##########################################################################################\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