/** @file\r
Entry point to a the PEI Core.\r
\r
-Copyright (c) 2006 - 2008, Intel Corporation<BR>\r
-All rights reserved. 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
-THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,\r
-WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.\r
+Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>\r
+SPDX-License-Identifier: BSD-2-Clause-Patent\r
\r
**/\r
\r
the PEI Services Table and the file handle for the PEI Core itself have been established.\r
If ProcessModuleEntryPointList() returns, then ASSERT() and halt the system.\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
+ @param SecCoreData Points to a data structure containing information about the\r
+ PEI core's operating environment, such as the size and\r
+ location of temporary RAM, the stack location and the BFV\r
+ 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
- descriptor with the end-tag EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST.\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 PpiList Points to a list of one or more PPI descriptors to be\r
+ installed initially by the PEI core. An empty PPI list\r
+ consists of a single descriptor with the end-tag\r
+ EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST.\r
+ As part of its initialization phase, the PEI Foundation will\r
+ add these SEC-hosted PPIs to its PPI database, such that both\r
+ the PEI Foundation and any modules can leverage the associated\r
+ service calls and/or code in these early PPIs.\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
{\r
ProcessModuleEntryPointList (SecCoreData, PpiList, NULL);\r
- \r
+\r
//\r
// Should never return\r
//\r
ASSERT(FALSE);\r
- CpuDeadLoop (); \r
+ CpuDeadLoop ();\r
}\r
\r
\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
- descriptor with the end-tag EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST.\r
- As part of its initialization phase, the PEI Foundation will add these\r
- SEC-hosted PPIs to its PPI database such that both the PEI Foundation\r
- and any modules can leverage the associated service calls and/or code\r
- in these early PPIs.\r
+ initially by the PEI core. An empty PPI list consists of\r
+ a single descriptor with the end-tag\r
+ EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST.\r
+ As part of its initialization phase, the PEI Foundation will\r
+ add these SEC-hosted PPIs to its PPI database, such that both\r
+ the PEI Foundationand any modules can leverage the associated\r
+ service calls and/or code in these early PPIs.\r
\r
**/\r
VOID\r