diff options
| author | qwang12 <qwang12@6f19259b-4bc3-4df7-8a09-765794883524> | 2007-10-10 02:08:22 +0000 |
|---|---|---|
| committer | qwang12 <qwang12@6f19259b-4bc3-4df7-8a09-765794883524> | 2007-10-10 02:08:22 +0000 |
| commit | 166152e85cd99bf4d3d9158b5c3455e4e0f7bb12 (patch) | |
| tree | 78cbdee059c1802f73e3d6a90ffd56153b014816 /MdePkg/Include/Library/PeiPiLib.h | |
| parent | 10dde96f9548bc11d01b46750293aba336d5d1c6 (diff) | |
| download | edk2-platforms-166152e85cd99bf4d3d9158b5c3455e4e0f7bb12.tar.xz | |
0) Change the PEI core behavior to not install FV HOB for each FV INFO PPI installed. This allows more freedom to platform developer to choose to expose which FV to PEI core or DXE core.
1) Split MdePkg/Include/Library/PiLib.h to DxePiLib.h and PeiPiLib.h. These two library classes are for DXE phase and PEI phase.
2) Update the API names in DxePiLib and PeiPiLib to be longer ones to be more meaningfull and to avoid name collisions.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@4067 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'MdePkg/Include/Library/PeiPiLib.h')
| -rw-r--r-- | MdePkg/Include/Library/PeiPiLib.h | 33 |
1 files changed, 28 insertions, 5 deletions
diff --git a/MdePkg/Include/Library/PeiPiLib.h b/MdePkg/Include/Library/PeiPiLib.h index a34fd50c10..a1b472ac69 100644 --- a/MdePkg/Include/Library/PeiPiLib.h +++ b/MdePkg/Include/Library/PeiPiLib.h @@ -17,13 +17,36 @@ #include <Pi/PiFirmwareFile.h>
+/**
+ Install a EFI_PEI_FIRMWARE_VOLUME_INFO PPI to inform PEI core about the existence of a new Firmware Volume.
+
+ The function allocate the EFI_PEI_PPI_DESCRIPTOR structure and update the fields accordingly to parameter passed
+ in and install the PPI.
+
+ @param FvStart Unique identifier of the format of the memory-mapped firmware volume. If NULL is specified,
+ EFI_FIRMWARE_FILE_SYSTEM2_GUID is used as the Format GUID.
+ @param FvInfo Points to a buffer which allows the EFI_PEI_FIRMWARE_VOLUME_PPI to
+ process the volume. The format of this buffer is specific to the FvFormat. For
+ memory-mapped firmware volumes, this typically points to the first byte of the
+ firmware volume.
+ @param FvInfoSize Size of the data provided by FvInfo. For memory-mapped firmware volumes, this is
+ typically the size of the firmware volume.
+ @param ParentFvName, ParentFileName If the firmware volume originally came from a firmware file, then these point to the
+ parent firmware volume name and firmware volume file. If it did not originally come
+ from a firmware file, these should be NULL
+
+ @retval VOID
+
+ **/
+
VOID
EFIAPI
-PeiPiLibBuildPiFvInfoPpi (
- IN EFI_PHYSICAL_ADDRESS FvStart,
- IN UINT64 FvLength,
- IN EFI_GUID *ParentFvName,
- IN EFI_GUID *PraentFileName
+PiLibInstallFvInfoPpi (
+ IN EFI_GUID *FvFormat, OPTIONAL
+ IN VOID *FvInfo,
+ IN UINT32 FvInfoSize,
+ IN EFI_GUID *ParentFvName, OPTIONAL
+ IN EFI_GUID *PraentFileName OPTIONAL
);
#endif
|