\r
\r
/**\r
- Searches the FFS file the the currently executing module was loaded from and returns the first matching FFS section.\r
+ Searches the FFS file the currently executing module was loaded from and returns the first matching FFS section.\r
\r
This function searches the FFS file that the currently executing module was loaded from for a FFS sections of type SectionType.\r
If the FFS file contains at least SectionInstance instances of the FFS section specified by SectionType,\r
If GetInfoHandler is NULL, then ASSERT().\r
If DecodeHandler is NULL, then ASSERT().\r
\r
- @param[in] SectionGuid A pointer to the GUID associated with the the handlers\r
+ @param[in] SectionGuid A pointer to the GUID associated with the handlers\r
of the GUIDed section type being registered.\r
@param[in] GetInfoHandler The pointer to a function that examines a GUIDed section and returns the\r
size of the decoded buffer and the size of an optional scratch buffer\r
Examines a GUIDed section specified by InputSection.\r
If GUID for InputSection does not match any of the GUIDs registered through ExtractGuidedSectionRegisterHandlers(),\r
then RETURN_UNSUPPORTED is returned.\r
- If the GUID of InputSection does match the GUID that this handler supports, then the the associated handler\r
+ If the GUID of InputSection does match the GUID that this handler supports, then the associated handler\r
of type EXTRACT_GUIDED_SECTION_GET_INFO_HANDLER that was registered with ExtractGuidedSectionRegisterHandlers()\r
- is used to retrieve the OututBufferSize, ScratchSize, and Attributes values. The return status from the handler of\r
+ is used to retrieve the OutputBufferSize, ScratchSize, and Attributes values. The return status from the handler of\r
type EXTRACT_GUIDED_SECTION_GET_INFO_HANDLER is returned.\r
\r
If InputSection is NULL, then ASSERT().\r
Decodes the GUIDed section specified by InputSection.\r
If GUID for InputSection does not match any of the GUIDs registered through ExtractGuidedSectionRegisterHandlers(),\r
then RETURN_UNSUPPORTED is returned.\r
- If the GUID of InputSection does match the GUID that this handler supports, then the the associated handler\r
+ If the GUID of InputSection does match the GUID that this handler supports, then the associated handler\r
of type EXTRACT_GUIDED_SECTION_DECODE_HANDLER that was registered with ExtractGuidedSectionRegisterHandlers()\r
is used to decode InputSection into the buffer specified by OutputBuffer and the authentication status of this\r
decode operation is returned in AuthenticationStatus. If the decoded buffer is identical to the data in InputSection,\r
\r
If SectionGuid is NULL, then ASSERT().\r
\r
- @param[in] SectionGuid A pointer to the GUID associated with the handlersof the GUIDed\r
+ @param[in] SectionGuid A pointer to the GUID associated with the handlers of the GUIDed\r
section type being retrieved.\r
@param[out] GetInfoHandler Pointer to a function that examines a GUIDed section and returns\r
the size of the decoded buffer and the size of an optional scratch\r
/** @file\r
- HOB Library implemenation for Dxe Phase.\r
+ HOB Library implementation for Dxe Phase.\r
\r
Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>\r
SPDX-License-Identifier: BSD-2-Clause-Patent\r
#include "DxeCpuIo2LibInternal.h"\r
\r
//\r
-// Globle varible to cache pointer to CpuIo2 protocol.\r
+// Global variable to cache pointer to CpuIo2 protocol.\r
//\r
EFI_CPU_IO2_PROTOCOL *mCpuIo = NULL;\r
\r
# Note: A driver of type DXE_RUNTIME_DRIVER and DXE_SMM_DRIVER can only use this DxePcdLib\r
# in their initialization without any issues to access Dynamic and DynamicEx PCD. They can't\r
# access Dynamic and DynamicEx PCD in the implementation of runtime services and SMI handlers.\r
-# Because EFI_PCD_PROTOCOL is DXE protocol that is not aviable in OS runtime phase.\r
+# Because EFI_PCD_PROTOCOL is DXE protocol that is not available in OS runtime phase.\r
#\r
# Copyright (c) 2007 - 2018, Intel Corporation. All rights reserved.<BR>\r
#\r
\r
#string STR_MODULE_ABSTRACT #language en-US "PCD Library using PCD Protocol"\r
\r
-#string STR_MODULE_DESCRIPTION #language en-US "There are two PCD protocols: 1) PCD_PROTOCOL It is an EDKII implementation that supporst Dynamic/DynamicEx PCDs. 2) EFI_PCD_PROTOCOL It is defined by PI Specification 1.2, Vol 3, which only support dynamicEx type PCD. For dynamicEx type PCDs, it is compatible between PCD_PROTOCOL and EFI_PCD_PROTOCOL. This library instance uses the PCD_PROTOCOL to handle dynamic PCD requests and uses EFI_PCD_PROTOCOL to handle DynamicEx type PCDs."\r
+#string STR_MODULE_DESCRIPTION #language en-US "There are two PCD protocols: 1) PCD_PROTOCOL It is an EDKII implementation that supports Dynamic/DynamicEx PCDs. 2) EFI_PCD_PROTOCOL It is defined by PI Specification 1.2, Vol 3, which only support dynamicEx type PCD. For dynamicEx type PCDs, it is compatible between PCD_PROTOCOL and EFI_PCD_PROTOCOL. This library instance uses the PCD_PROTOCOL to handle dynamic PCD requests and uses EFI_PCD_PROTOCOL to handle DynamicEx type PCDs."\r
\r
Address = GetPciExpressAddress (Address & 0x0ffff000);\r
\r
//\r
- // See if Address has already been registerd for runtime access\r
+ // See if Address has already been registered for runtime access\r
//\r
for (Index = 0; Index < mDxeRuntimePciExpressLibNumberOfRuntimeRanges; Index++) {\r
if (mDxeRuntimePciExpressLibRegistrationTable[Index].PhysicalAddress == Address) {\r
Size into the buffer specified by Buffer. This function only allows the PCI\r
configuration registers from a single PCI function to be read. Size is\r
returned. When possible 32-bit PCI configuration read cycles are used to read\r
- from StartAdress to StartAddress + Size. Due to alignment restrictions, 8-bit\r
+ from StartAddress to StartAddress + Size. Due to alignment restrictions, 8-bit\r
and 16-bit PCI configuration read cycles may be used at the beginning and the\r
end of the range.\r
\r
Size from the buffer specified by Buffer. This function only allows the PCI\r
configuration registers from a single PCI function to be written. Size is\r
returned. When possible 32-bit PCI configuration write cycles are used to\r
- write from StartAdress to StartAddress + Size. Due to alignment restrictions,\r
+ write from StartAddress to StartAddress + Size. Due to alignment restrictions,\r
8-bit and 16-bit PCI configuration write cycles may be used at the beginning\r
and the end of the range.\r
\r
/**\r
Identify the device handle from which the Image is loaded from. As this device handle is passed to\r
GetSectionFromFv as the identifier for a Firmware Volume, an EFI_FIRMWARE_VOLUME2_PROTOCOL\r
- protocol instance should be located succesfully by calling gBS->HandleProtocol ().\r
+ protocol instance should be located successfully by calling gBS->HandleProtocol ().\r
\r
This function locates the EFI_LOADED_IMAGE_PROTOCOL instance installed\r
on ImageHandle. It then returns EFI_LOADED_IMAGE_PROTOCOL.DeviceHandle.\r
Section type and instance number from the specified Firmware Volume.\r
\r
This functions first locate the EFI_FIRMWARE_VOLUME2_PROTOCOL protocol instance on FvHandle in order to\r
- carry out the Firmware Volume read operation. The function then reads the Firmware Section found sepcifed\r
+ carry out the Firmware Volume read operation. The function then reads the Firmware Section found specified\r
by NameGuid, SectionType and SectionInstance.\r
\r
The details of this search order is defined in description of EFI_FIRMWARE_VOLUME2_PROTOCOL.ReadSection ()\r
@param SectionType The Firmware Section type.\r
@param SectionInstance The instance number of Firmware Section to\r
read from starting from 0.\r
- @param Buffer On output, Buffer contains the the data read\r
+ @param Buffer On output, Buffer contains the data read\r
from the section in the Firmware File found.\r
@param Size On output, the size of Buffer.\r
\r
\r
\r
/**\r
- Searches the FFS file the the currently executing module was loaded from and returns the first matching FFS section.\r
+ Searches the FFS file the currently executing module was loaded from and returns the first matching FFS section.\r
\r
This function searches the FFS file that the currently executing module was loaded from for a FFS sections of type SectionType.\r
If the FFS file contains at least SectionInstance instances of the FFS section specified by SectionType,\r
selection. If FALSE, then FilePath must\r
match an exact file to be loaded.\r
@param[in] FilePath The pointer to the device path of the file\r
- that is absracted to the file buffer.\r
+ that is abstracted to the file buffer.\r
@param[out] FileSize The pointer to the size of the abstracted\r
file buffer.\r
@param[out] AuthenticationStatus Pointer to the authentication status.\r
}\r
//\r
// Parse each MEDIA_FILEPATH_DP node. There may be more than one, since the\r
- // directory information and filename can be seperate. The goal is to inch\r
+ // directory information and filename can be separate. The goal is to inch\r
// our way down each device path node and close the previous node\r
//\r
DevicePathNode = TempDevicePathNode;\r
Please attention this library instance can not be used util EFI_SYSTEM_TABLE was\r
initialized.\r
\r
- This library contains contruct function to retrieve EFI_DXE_SERIVCE, this construct\r
+ This library contains construct function to retrieve EFI_DXE_SERVICE, this construct\r
function will be invoked in DXE driver's autogen file.\r
\r
Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>\r
\r
\r
//\r
-// Globle varible to cache pointer to Smbus protocol.\r
+// Global variable to cache pointer to Smbus protocol.\r
//\r
EFI_SMBUS_HC_PROTOCOL *mSmbus = NULL;\r
\r
projects / mirror_edk2.git / commitdiff