/** @file\r
Module entry point library for PEI core.\r
\r
-Copyright (c) 2006 - 2008, Intel Corporation<BR>\r
-All rights reserved. This program and the accompanying materials\r
+Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>\r
+This program and the accompanying materials\r
are licensed and made available under the terms and conditions of the BSD License\r
which accompanies this distribution. The full text of the license may be found at\r
http://opensource.org/licenses/bsd-license.php\r
\r
@param SecCoreData Points to a data structure containing information about the PEI\r
core's operating environment, such as the size and location of\r
- temporary RAM, the stack location and the BFV location. \r
+ temporary RAM, the stack location and the BFV location.\r
\r
@param PpiList Points to a list of one or more PPI descriptors to be installed\r
initially by the PEI core. An empty PPI list consists of a single\r
\r
**/\r
VOID\r
-EFIAPI \r
+EFIAPI\r
_ModuleEntryPoint(\r
IN CONST EFI_SEC_PEI_HAND_OFF *SecCoreData,\r
IN CONST EFI_PEI_PPI_DESCRIPTOR *PpiList\r
\r
@param SecCoreData Points to a data structure containing information about the PEI core's\r
operating environment, such as the size and location of temporary RAM,\r
- the stack location and the BFV location. \r
+ the stack location and the BFV location.\r
\r
@param PpiList Points to a list of one or more PPI descriptors to be installed\r
initially by the PEI core. An empty PPI list consists of a single\r
This function must be called by the PEI Core once an initial PEI Services Table has been established.\r
This function calls the set of library constructors for the set of library instances that a\r
module depends on. This include library instances that a module depends on directly and library\r
- instances that a module depends on indirectly through other libraries. \r
+ instances that a module depends on indirectly through other libraries.\r
This function is autogenerated by build tools and those build tools are responsible for collecting\r
- the set of library instances, determine which ones have constructors, and calling the library\r
- constructors in the proper order based upon each of the library instances own dependencies.\r
+ the set of library instances, determining which ones have constructors, and calling the library\r
+ constructors in the proper order based upon the dependencies of each of the library instances.\r
The PEI Core must call this function with a NULL FileHandle value as soon as the initial PEI\r
Services Table has been established.\r
\r
- @param FileHandle Handle of the file being invoked.Type EFI_PEI_FILE_HANDLE is defined in FfsFindNextFile().\r
+ @param FileHandle Handle of the file being invoked.\r
@param PeiServices Describes the list of possible PEI Services.\r
\r
**/\r
Autogenerated function that calls a set of module entry points.\r
\r
This function must be called by _ModuleEntryPoint().\r
- This function calls the set of module entry points. \r
+ This function calls the set of module entry points.\r
This function is autogenerated by build tools and those build tools are responsible\r
for collecting the module entry points and calling them in a specified order.\r
\r
@param SecCoreData Points to a data structure containing information about the PEI\r
core's operating environment, such as the size and location of\r
- temporary RAM, the stack location and the BFV location. \r
+ temporary RAM, the stack location and the BFV location.\r
\r
@param PpiList Points to a list of one or more PPI descriptors to be installed\r
initially by the PEI core. An empty PPI list consists of a single\r
As part of its initialization phase, the PEI Foundation will add\r
these SEC-hosted PPIs to its PPI database such that both the PEI\r
Foundation and any modules can leverage the associated service calls\r
- and/or code in these early PPIs. \r
- @param OldCoreData Pointer to Original startup information.\r
+ and/or code in these early PPIs.\r
+ @param Context A pointer to a private context structure defined by the PEI Core\r
+ implementation. The implementation of _ModuleEntryPoint() must set\r
+ this parameter is NULL to indicate that this is the first PEI phase.\r
\r
**/\r
VOID\r
ProcessModuleEntryPointList (\r
IN CONST EFI_SEC_PEI_HAND_OFF *SecCoreData,\r
IN CONST EFI_PEI_PPI_DESCRIPTOR *PpiList,\r
- IN VOID *OldCoreData\r
+ IN VOID *Context\r
);\r
\r
#endif\r