\r
\r
/**\r
- Find ACPI tables in an FV and install them. \r
+ Find ACPI tables in an FV and install them.\r
\r
This is now a fall-back path. Normally, we will search for tables provided\r
by the VMM first.\r
If that fails, we use this function to load the ACPI tables from an FV. The\r
sources for the FV based tables is located under OvmfPkg/AcpiTables.\r
\r
- @param AcpiTable Protocol instance pointer \r
+ @param AcpiTable Protocol instance pointer\r
\r
**/\r
EFI_STATUS\r
\r
SPDX-License-Identifier: BSD-2-Clause-Patent\r
\r
-**/ \r
+**/\r
\r
#include "AcpiPlatform.h"\r
#include <Library/BaseLib.h>\r
}\r
\r
//\r
- // If XSDT table is find, just install its tables. \r
+ // If XSDT table is find, just install its tables.\r
// Otherwise, try to find and install the RSDT tables.\r
//\r
if (XenAcpiRsdpStructurePtr->XsdtAddress) {\r
//\r
- // Retrieve the addresses of XSDT and \r
+ // Retrieve the addresses of XSDT and\r
// calculate the number of its table entries.\r
//\r
Xsdt = (EFI_ACPI_DESCRIPTION_HEADER *) (UINTN)\r
Rsdt = (EFI_ACPI_DESCRIPTION_HEADER *) (UINTN)\r
XenAcpiRsdpStructurePtr->RsdtAddress;\r
NumberOfTableEntries = (Rsdt->Length -\r
- sizeof (EFI_ACPI_DESCRIPTION_HEADER)) / \r
+ sizeof (EFI_ACPI_DESCRIPTION_HEADER)) /\r
sizeof (UINT32);\r
\r
//\r
/** @file\r
FACS Table\r
- \r
+\r
Copyright (c) 2008 - 2012, Intel Corporation. All rights reserved.<BR>\r
SPDX-License-Identifier: BSD-2-Clause-Patent\r
\r
-**/ \r
+**/\r
\r
#include <IndustryStandard/Acpi.h>\r
\r
)\r
{\r
//\r
- // Reference the table being generated to prevent the optimizer from removing the \r
+ // Reference the table being generated to prevent the optimizer from removing the\r
// data structure from the exeutable\r
//\r
return (VOID*)&FACS;\r
///** @file\r
-// \r
+//\r
// Browser formset.\r
-// \r
+//\r
// Copyright (c) 2015, Intel Corporation. All rights reserved.<BR>\r
// SPDX-License-Identifier: BSD-2-Clause-Patent\r
-// \r
+//\r
//**/\r
\r
#include "LegacyBootMaintUiVfr.h"\r
title = STRING_TOKEN(STR_LEGACY_BOOT_PROMPT),\r
help = STRING_TOKEN(STR_LEGACY_BOOT_HELP),\r
classguid = EFI_IFR_BOOT_MAINTENANCE_GUID,\r
- \r
+\r
varstore LEGACY_BOOT_NV_DATA,\r
varid = VARSTORE_ID_LEGACY_BOOT,\r
name = LegacyBootData,\r
guid = LEGACY_BOOT_OPTION_FORMSET_GUID;\r
- \r
+\r
form formid = LEGACY_BOOT_FORM_ID,\r
title = STRING_TOKEN(STR_LEGACY_BOOT_PROMPT);\r
- \r
+\r
goto LEGACY_ORDER_CHANGE_FORM_ID,\r
prompt = STRING_TOKEN(STR_FORM_FLOPPY_BOOT_TITLE),\r
help = STRING_TOKEN(STR_FORM_FLOPPY_BOOT_HELP),\r
help = STRING_TOKEN(STR_FORM_BEV_BOOT_HELP),\r
flags = INTERACTIVE,\r
key = FORM_BEV_BOOT_ID;\r
- \r
+\r
endform;\r
\r
form formid = LEGACY_ORDER_CHANGE_FORM_ID,\r
title = STRING_TOKEN(STR_ORDER_CHANGE_PROMPT);\r
- \r
+\r
label FORM_BOOT_LEGACY_DEVICE_ID;\r
label FORM_BOOT_LEGACY_LABEL_END;\r
- \r
+\r
endform;\r
\r
endformset;\r
/******************************************************************************\r
* xen-x86_32.h\r
- * \r
+ *\r
* Guest OS interface to x86 32-bit Xen.\r
- * \r
+ *\r
* SPDX-License-Identifier: MIT\r
*\r
* Copyright (c) 2004-2007, K A Fraser\r
/******************************************************************************\r
* xen-x86_64.h\r
- * \r
+ *\r
* Guest OS interface to x86 64-bit Xen.\r
- * \r
+ *\r
* SPDX-License-Identifier: MIT\r
*\r
* Copyright (c) 2004-2006, K A Fraser\r
/******************************************************************************\r
* arch-x86/xen.h\r
- * \r
+ *\r
* Guest OS interface to x86 Xen.\r
- * \r
+ *\r
* SPDX-License-Identifier: MIT\r
*\r
* Copyright (c) 2004-2006, K A Fraser\r
*/\r
#define HVM_PARAM_ACPI_IOPORTS_LOCATION 19\r
\r
-/* Enable blocking memory events, async or sync (pause vcpu until response) \r
+/* Enable blocking memory events, async or sync (pause vcpu until response)\r
* onchangeonly indicates messages only on a change of value */\r
#define HVM_PARAM_MEMORY_EVENT_CR0 20\r
#define HVM_PARAM_MEMORY_EVENT_CR3 21\r
/******************************************************************************\r
* protocols.h\r
- * \r
+ *\r
* SPDX-License-Identifier: MIT\r
*/\r
\r
/******************************************************************************\r
* ring.h\r
- * \r
+ *\r
* Shared producer-consumer ring macros.\r
*\r
* SPDX-License-Identifier: MIT\r
/*\r
* Calculate size of a shared ring, given the total available space for the\r
* ring and indexes (_sz), and the name tag of the request/response structure.\r
- * A ring contains as many entries as will fit, rounded down to the nearest \r
+ * A ring contains as many entries as will fit, rounded down to the nearest\r
* power of two (so we can mask with (size-1) to loop around).\r
*/\r
#define __CONST_RING_SIZE(_s, _sz) \\r
\r
/*\r
* Macros to make the correct C datatypes for a new kind of ring.\r
- * \r
+ *\r
* To make a new ring datatype, you need to have two message structures,\r
* let's say request_t, and response_t already defined.\r
*\r
*\r
* These expand out to give you a set of types, as you can see below.\r
* The most important of these are:\r
- * \r
+ *\r
* mytag_sring_t - The shared ring.\r
* mytag_front_ring_t - The 'front' half of the ring.\r
* mytag_back_ring_t - The 'back' half of the ring.\r
\r
/*\r
* Macros for manipulating rings.\r
- * \r
- * FRONT_RING_whatever works on the "front end" of a ring: here \r
+ *\r
+ * FRONT_RING_whatever works on the "front end" of a ring: here\r
* requests are pushed on to the ring and responses taken off it.\r
- * \r
- * BACK_RING_whatever works on the "back end" of a ring: here \r
+ *\r
+ * BACK_RING_whatever works on the "back end" of a ring: here\r
* requests are taken off the ring and responses put on.\r
- * \r
- * N.B. these macros do NO INTERLOCKS OR FLOW CONTROL. \r
- * This is OK in 1-for-1 request-response situations where the \r
+ *\r
+ * N.B. these macros do NO INTERLOCKS OR FLOW CONTROL.\r
+ * This is OK in 1-for-1 request-response situations where the\r
* requestor (front end) never has more than RING_SIZE()-1\r
* outstanding requests.\r
*/\r
\r
/*\r
* Notification hold-off (req_event and rsp_event):\r
- * \r
+ *\r
* When queueing requests or responses on a shared ring, it may not always be\r
* necessary to notify the remote end. For example, if requests are in flight\r
* in a backend, the front may be able to queue further requests without\r
* notifying the back (if the back checks for new requests when it queues\r
* responses).\r
- * \r
+ *\r
* When enqueuing requests or responses:\r
- * \r
+ *\r
* Use RING_PUSH_{REQUESTS,RESPONSES}_AND_CHECK_NOTIFY(). The second argument\r
* is a boolean return value. True indicates that the receiver requires an\r
* asynchronous notification.\r
- * \r
+ *\r
* After dequeuing requests or responses (before sleeping the connection):\r
- * \r
+ *\r
* Use RING_FINAL_CHECK_FOR_REQUESTS() or RING_FINAL_CHECK_FOR_RESPONSES().\r
* The second argument is a boolean return value. True indicates that there\r
* are pending messages on the ring (i.e., the connection should not be put\r
* to sleep).\r
- * \r
+ *\r
* These macros will set the req_event/rsp_event field to trigger a\r
* notification on the very next message that is enqueued. If you want to\r
* create batches of work (i.e., only receive a notification after several\r
/******************************************************************************\r
* memory.h\r
- * \r
+ *\r
* Memory reservation and information.\r
- * \r
+ *\r
* SPDX-License-Identifier: MIT\r
*\r
* Copyright (c) 2005, Keir Fraser <keir@xensource.com>\r
/******************************************************************************\r
* xen-compat.h\r
- * \r
+ *\r
* Guest OS interface to Xen. Compatibility layer.\r
- * \r
+ *\r
* SPDX-License-Identifier: MIT\r
*\r
* Copyright (c) 2006, Christian Limpach\r
/******************************************************************************\r
* xen.h\r
- * \r
+ *\r
* Guest OS interface to Xen.\r
- * \r
+ *\r
* SPDX-License-Identifier: MIT\r
*\r
* Copyright (c) 2004, K A Fraser\r
struct vcpu_info {\r
/*\r
* 'evtchn_upcall_pending' is written non-zero by Xen to indicate\r
- * a pending notification for a particular VCPU. It is then cleared \r
+ * a pending notification for a particular VCPU. It is then cleared\r
* by the guest OS /before/ checking for pending work, thus avoiding\r
* a set-and-check race. Note that the mask is only accessed by Xen\r
* on the CPU that is currently hosting the VCPU. This means that the\r
* 3. Virtual interrupts ('events'). A domain can bind an event-channel\r
* port to a virtual interrupt source, such as the virtual-timer\r
* device or the emergency console.\r
- * \r
+ *\r
* Event channels are addressed by a "port index". Each channel is\r
* associated with two bits of information:\r
* 1. PENDING -- notifies the domain that there is a pending notification\r
* becomes pending while the channel is masked then the 'edge' is lost\r
* (i.e., when the channel is unmasked, the guest must manually handle\r
* pending notifications as no upcall will be scheduled by Xen).\r
- * \r
+ *\r
* To expedite scanning of pending notifications, any 0->1 pending\r
* transition on an unmasked channel causes a corresponding bit in a\r
* per-vcpu selector word to be set. Each bit in the selector covers a\r
/** @file\r
SMRAM Save State Map Definitions.\r
\r
-SMRAM Save State Map definitions based on contents of the \r
+SMRAM Save State Map definitions based on contents of the\r
Intel(R) 64 and IA-32 Architectures Software Developer's Manual\r
Volume 3C, Section 34.4 SMRAM\r
Volume 3C, Section 34.5 SMI Handler Execution Environment\r
}\r
\r
/**\r
- Registers a PCI device so PCI configuration registers may be accessed after \r
+ Registers a PCI device so PCI configuration registers may be accessed after\r
SetVirtualAddressMap().\r
- \r
- Registers the PCI device specified by Address so all the PCI configuration registers \r
+\r
+ Registers the PCI device specified by Address so all the PCI configuration registers\r
associated with that PCI device may be accessed after SetVirtualAddressMap() is called.\r
- \r
+\r
If Address > 0x0FFFFFFF, then ASSERT().\r
\r
@param Address The address that encodes the PCI Bus, Device, Function and\r
Register.\r
- \r
+\r
@retval RETURN_SUCCESS The PCI device was registered for runtime access.\r
- @retval RETURN_UNSUPPORTED An attempt was made to call this function \r
+ @retval RETURN_UNSUPPORTED An attempt was made to call this function\r
after ExitBootServices().\r
@retval RETURN_UNSUPPORTED The resources required to access the PCI device\r
at runtime could not be mapped.\r
\r
@param MemoryType Memory type of memory to allocate.\r
@param Size Size of memory to allocate.\r
- \r
+\r
@return Allocated address for output.\r
\r
**/\r
StartOfEntries = ((LOCK_BOX_ENTRY *) (mLockBoxGlobal + 1));\r
NumEntries = ((PcdGet32 (PcdOvmfLockBoxStorageSize) - sizeof (LOCK_BOX_GLOBAL)) /\r
sizeof (LOCK_BOX_ENTRY));\r
- EndOfEntries = StartOfEntries + NumEntries; \r
+ EndOfEntries = StartOfEntries + NumEntries;\r
if (mLockBoxGlobal->Signature != LOCK_BOX_GLOBAL_SIGNATURE) {\r
//\r
// Note: This code depends on the lock box being cleared in early\r
/** @file\r
- \r
+\r
Copyright (c) 2006 - 2014, Intel Corporation. All rights reserved.<BR>\r
\r
SPDX-License-Identifier: BSD-2-Clause-Patent\r
/**\r
\r
This function provides a platform-specific method to detect whether the platform\r
- is operating by a physically present user. \r
+ is operating by a physically present user.\r
\r
Programmatic changing of platform security policy (such as disable Secure Boot,\r
or switch between Standard/Custom Secure Boot mode) MUST NOT be possible during\r
\r
NOTE THAT: This function cannot depend on any EFI Variable Service since they are\r
not available when this function is called in AuthenticateVariable driver.\r
- \r
+\r
@retval TRUE The platform is operated by a physically present user.\r
@retval FALSE The platform is NOT operated by a physically present user.\r
\r
\r
/**\r
Selects a firmware configuration item for reading.\r
- \r
+\r
Following this call, any data read from this item will start from\r
the beginning of the configuration item's data.\r
\r
*Handle = OutHandle;\r
return EFI_SUCCESS;\r
}\r
- \r
+\r
DEBUG ((EFI_D_ERROR, "%a: Failed to install the EFI_DEVICE_PATH and "\r
"XENIO_PROTOCOL protocols on handle %p (Status == %r)\n",\r
__FUNCTION__, OutHandle, Status));\r
\r
/**\r
Connects to the Hypervisor.\r
- \r
+\r
@param XenLeaf CPUID index used to connect.\r
\r
@return EFI_STATUS\r
@param DriverName A pointer to the Unicode string to return. This Unicode string\r
is the name of the driver specified by This in the language\r
specified by Language.\r
- \r
+\r
@retval EFI_SUCCESS The Unicode string for the Driver specified by This\r
and the language specified by Language was returned\r
in DriverName.\r
\r
/**\r
Retrieves a Unicode string that is the user readable name of the controller\r
- that is being managed by an UEFI Driver. \r
+ that is being managed by an UEFI Driver.\r
\r
@param This A pointer to the EFI_COMPONENT_NAME_PROTOCOL instance.\r
@param ControllerHandle The handle of a controller that the driver specified by\r
ControllerHandle and ChildHandle in the language\r
specified by Language from the point of view of the\r
driver specified by This.\r
- \r
+\r
@retval EFI_SUCCESS The Unicode string for the user readable name in the\r
language specified by Language for the driver\r
specified by This was returned in DriverName.\r
UINT32 Data;\r
\r
ASSERT (PciIo != NULL);\r
- \r
+\r
Data = 0;\r
\r
PciIo->Mem.Read (\r
/**\r
The Entry Point of module. It follows the standard UEFI driver model.\r
\r
- @param[in] ImageHandle The firmware allocated handle for the EFI image. \r
+ @param[in] ImageHandle The firmware allocated handle for the EFI image.\r
@param[in] SystemTable A pointer to the EFI System Table.\r
- \r
+\r
@retval EFI_SUCCESS The entry point is executed successfully.\r
@retval other Some error occurs when executing this entry point.\r
\r
}\r
\r
/**\r
- This routine is called right after the .Supported() called and \r
+ This routine is called right after the .Supported() called and\r
Start this driver on ControllerHandle.\r
\r
@param This Protocol instance pointer.\r
//\r
/**\r
Returns the information about the specified IDE channel.\r
- \r
+\r
This function can be used to obtain information about a particular IDE channel.\r
- The driver entity uses this information during the enumeration process. \r
- \r
- If Enabled is set to FALSE, the driver entity will not scan the channel. Note \r
+ The driver entity uses this information during the enumeration process.\r
+\r
+ If Enabled is set to FALSE, the driver entity will not scan the channel. Note\r
that it will not prevent an operating system driver from scanning the channel.\r
- \r
- For most of today's controllers, MaxDevices will either be 1 or 2. For SATA \r
- controllers, this value will always be 1. SATA configurations can contain SATA \r
+\r
+ For most of today's controllers, MaxDevices will either be 1 or 2. For SATA\r
+ controllers, this value will always be 1. SATA configurations can contain SATA\r
port multipliers. SATA port multipliers behave like SATA bridges and can support\r
- up to 16 devices on the other side. If a SATA port out of the IDE controller \r
- is connected to a port multiplier, MaxDevices will be set to the number of SATA \r
- devices that the port multiplier supports. Because today's port multipliers \r
- support up to fifteen SATA devices, this number can be as large as fifteen. The IDE \r
- bus driver is required to scan for the presence of port multipliers behind an SATA \r
- controller and enumerate up to MaxDevices number of devices behind the port \r
- multiplier. \r
- \r
- In this context, the devices behind a port multiplier constitute a channel. \r
- \r
+ up to 16 devices on the other side. If a SATA port out of the IDE controller\r
+ is connected to a port multiplier, MaxDevices will be set to the number of SATA\r
+ devices that the port multiplier supports. Because today's port multipliers\r
+ support up to fifteen SATA devices, this number can be as large as fifteen. The IDE\r
+ bus driver is required to scan for the presence of port multipliers behind an SATA\r
+ controller and enumerate up to MaxDevices number of devices behind the port\r
+ multiplier.\r
+\r
+ In this context, the devices behind a port multiplier constitute a channel.\r
+\r
@param[in] This The pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Channel Zero-based channel number.\r
- @param[out] Enabled TRUE if this channel is enabled. Disabled channels \r
+ @param[out] Enabled TRUE if this channel is enabled. Disabled channels\r
are not scanned to see if any devices are present.\r
@param[out] MaxDevices The maximum number of IDE devices that the bus driver\r
- can expect on this channel. For the ATA/ATAPI \r
- specification, version 6, this number will either be \r
- one or two. For Serial ATA (SATA) configurations with a \r
+ can expect on this channel. For the ATA/ATAPI\r
+ specification, version 6, this number will either be\r
+ one or two. For Serial ATA (SATA) configurations with a\r
port multiplier, this number can be as large as fifteen.\r
\r
@retval EFI_SUCCESS Information was returned without any errors.\r
/**\r
The notifications from the driver entity that it is about to enter a certain\r
phase of the IDE channel enumeration process.\r
- \r
- This function can be used to notify the IDE controller driver to perform \r
- specific actions, including any chipset-specific initialization, so that the \r
- chipset is ready to enter the next phase. Seven notification points are defined \r
- at this time. \r
- \r
- More synchronization points may be added as required in the future. \r
+\r
+ This function can be used to notify the IDE controller driver to perform\r
+ specific actions, including any chipset-specific initialization, so that the\r
+ chipset is ready to enter the next phase. Seven notification points are defined\r
+ at this time.\r
+\r
+ More synchronization points may be added as required in the future.\r
\r
@param[in] This The pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Phase The phase during enumeration.\r
@retval EFI_SUCCESS The notification was accepted without any errors.\r
@retval EFI_UNSUPPORTED Phase is not supported.\r
@retval EFI_INVALID_PARAMETER Channel is invalid (Channel >= ChannelCount).\r
- @retval EFI_NOT_READY This phase cannot be entered at this time; for \r
- example, an attempt was made to enter a Phase \r
- without having entered one or more previous \r
+ @retval EFI_NOT_READY This phase cannot be entered at this time; for\r
+ example, an attempt was made to enter a Phase\r
+ without having entered one or more previous\r
Phase.\r
\r
**/\r
/**\r
Submits the device information to the IDE controller driver.\r
\r
- This function is used by the driver entity to pass detailed information about \r
- a particular device to the IDE controller driver. The driver entity obtains \r
+ This function is used by the driver entity to pass detailed information about\r
+ a particular device to the IDE controller driver. The driver entity obtains\r
this information by issuing an ATA or ATAPI IDENTIFY_DEVICE command. IdentifyData\r
- is the pointer to the response data buffer. The IdentifyData buffer is owned \r
- by the driver entity, and the IDE controller driver must make a local copy \r
- of the entire buffer or parts of the buffer as needed. The original IdentifyData \r
+ is the pointer to the response data buffer. The IdentifyData buffer is owned\r
+ by the driver entity, and the IDE controller driver must make a local copy\r
+ of the entire buffer or parts of the buffer as needed. The original IdentifyData\r
buffer pointer may not be valid when\r
- \r
+\r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.CalculateMode() or\r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyMode() is called at a later point.\r
- \r
- The IDE controller driver may consult various fields of EFI_IDENTIFY_DATA to \r
- compute the optimum mode for the device. These fields are not limited to the \r
- timing information. For example, an implementation of the IDE controller driver \r
- may examine the vendor and type/mode field to match known bad drives. \r
- \r
- The driver entity may submit drive information in any order, as long as it \r
- submits information for all the devices belonging to the enumeration group \r
+\r
+ The IDE controller driver may consult various fields of EFI_IDENTIFY_DATA to\r
+ compute the optimum mode for the device. These fields are not limited to the\r
+ timing information. For example, an implementation of the IDE controller driver\r
+ may examine the vendor and type/mode field to match known bad drives.\r
+\r
+ The driver entity may submit drive information in any order, as long as it\r
+ submits information for all the devices belonging to the enumeration group\r
before EFI_IDE_CONTROLLER_INIT_PROTOCOL.CalculateMode() is called for any device\r
in that enumeration group. If a device is absent, EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData()\r
- should be called with IdentifyData set to NULL. The IDE controller driver may \r
- not have any other mechanism to know whether a device is present or not. Therefore, \r
- setting IdentifyData to NULL does not constitute an error condition. \r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData() can be called only once for a \r
- given (Channel, Device) pair. \r
- \r
+ should be called with IdentifyData set to NULL. The IDE controller driver may\r
+ not have any other mechanism to know whether a device is present or not. Therefore,\r
+ setting IdentifyData to NULL does not constitute an error condition.\r
+ EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData() can be called only once for a\r
+ given (Channel, Device) pair.\r
+\r
@param[in] This A pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Channel Zero-based channel number.\r
@param[in] Device Zero-based device number on the Channel.\r
/**\r
Disqualifies specific modes for an IDE device.\r
\r
- This function allows the driver entity or other drivers (such as platform \r
+ This function allows the driver entity or other drivers (such as platform\r
drivers) to reject certain timing modes and request the IDE controller driver\r
- to recalculate modes. This function allows the driver entity and the IDE \r
- controller driver to negotiate the timings on a per-device basis. This function \r
- is useful in the case of drives that lie about their capabilities. An example \r
- is when the IDE device fails to accept the timing modes that are calculated \r
+ to recalculate modes. This function allows the driver entity and the IDE\r
+ controller driver to negotiate the timings on a per-device basis. This function\r
+ is useful in the case of drives that lie about their capabilities. An example\r
+ is when the IDE device fails to accept the timing modes that are calculated\r
by the IDE controller driver based on the response to the Identify Drive command.\r
\r
- If the driver entity does not want to limit the ATA timing modes and leave that \r
- decision to the IDE controller driver, it can either not call this function for \r
- the given device or call this function and set the Valid flag to FALSE for all \r
+ If the driver entity does not want to limit the ATA timing modes and leave that\r
+ decision to the IDE controller driver, it can either not call this function for\r
+ the given device or call this function and set the Valid flag to FALSE for all\r
modes that are listed in EFI_ATA_COLLECTIVE_MODE.\r
- \r
- The driver entity may disqualify modes for a device in any order and any number \r
+\r
+ The driver entity may disqualify modes for a device in any order and any number\r
of times.\r
- \r
- This function can be called multiple times to invalidate multiple modes of the \r
- same type (e.g., Programmed Input/Output [PIO] modes 3 and 4). See the ATA/ATAPI \r
- specification for more information on PIO modes. \r
- \r
+\r
+ This function can be called multiple times to invalidate multiple modes of the\r
+ same type (e.g., Programmed Input/Output [PIO] modes 3 and 4). See the ATA/ATAPI\r
+ specification for more information on PIO modes.\r
+\r
For Serial ATA (SATA) controllers, this member function can be used to disqualify\r
a higher transfer rate mode on a given channel. For example, a platform driver\r
- may inform the IDE controller driver to not use second-generation (Gen2) speeds \r
+ may inform the IDE controller driver to not use second-generation (Gen2) speeds\r
for a certain SATA drive.\r
- \r
+\r
@param[in] This The pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Channel The zero-based channel number.\r
@param[in] Device The zero-based device number on the Channel.\r
@retval EFI_INVALID_PARAMETER Channel is invalid (Channel >= ChannelCount).\r
@retval EFI_INVALID_PARAMETER Device is invalid.\r
@retval EFI_INVALID_PARAMETER IdentifyData is NULL.\r
- \r
+\r
**/\r
EFI_STATUS\r
EFIAPI\r
Returns the information about the optimum modes for the specified IDE device.\r
\r
This function is used by the driver entity to obtain the optimum ATA modes for\r
- a specific device. The IDE controller driver takes into account the following \r
+ a specific device. The IDE controller driver takes into account the following\r
while calculating the mode:\r
- The IdentifyData inputs to EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData()\r
- The BadModes inputs to EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyMode()\r
\r
- The driver entity is required to call EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData() \r
- for all the devices that belong to an enumeration group before calling \r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.CalculateMode() for any device in the same group. \r
- \r
- The IDE controller driver will use controller- and possibly platform-specific \r
- algorithms to arrive at SupportedModes. The IDE controller may base its \r
- decision on user preferences and other considerations as well. This function \r
- may be called multiple times because the driver entity may renegotiate the mode \r
+ The driver entity is required to call EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData()\r
+ for all the devices that belong to an enumeration group before calling\r
+ EFI_IDE_CONTROLLER_INIT_PROTOCOL.CalculateMode() for any device in the same group.\r
+\r
+ The IDE controller driver will use controller- and possibly platform-specific\r
+ algorithms to arrive at SupportedModes. The IDE controller may base its\r
+ decision on user preferences and other considerations as well. This function\r
+ may be called multiple times because the driver entity may renegotiate the mode\r
with the IDE controller driver using EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyMode().\r
- \r
- The driver entity may collect timing information for various devices in any \r
+\r
+ The driver entity may collect timing information for various devices in any\r
order. The driver entity is responsible for making sure that all the dependencies\r
- are satisfied. For example, the SupportedModes information for device A that \r
- was previously returned may become stale after a call to \r
+ are satisfied. For example, the SupportedModes information for device A that\r
+ was previously returned may become stale after a call to\r
EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyMode() for device B.\r
- \r
- The buffer SupportedModes is allocated by the callee because the caller does \r
- not necessarily know the size of the buffer. The type EFI_ATA_COLLECTIVE_MODE \r
- is defined in a way that allows for future extensibility and can be of variable \r
- length. This memory pool should be deallocated by the caller when it is no \r
- longer necessary. \r
- \r
- The IDE controller driver for a Serial ATA (SATA) controller can use this \r
- member function to force a lower speed (first-generation [Gen1] speeds on a \r
- second-generation [Gen2]-capable hardware). The IDE controller driver can \r
- also allow the driver entity to stay with the speed that has been negotiated \r
+\r
+ The buffer SupportedModes is allocated by the callee because the caller does\r
+ not necessarily know the size of the buffer. The type EFI_ATA_COLLECTIVE_MODE\r
+ is defined in a way that allows for future extensibility and can be of variable\r
+ length. This memory pool should be deallocated by the caller when it is no\r
+ longer necessary.\r
+\r
+ The IDE controller driver for a Serial ATA (SATA) controller can use this\r
+ member function to force a lower speed (first-generation [Gen1] speeds on a\r
+ second-generation [Gen2]-capable hardware). The IDE controller driver can\r
+ also allow the driver entity to stay with the speed that has been negotiated\r
by the physical layer.\r
- \r
+\r
@param[in] This The pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Channel A zero-based channel number.\r
@param[in] Device A zero-based device number on the Channel.\r
\r
@retval EFI_SUCCESS SupportedModes was returned.\r
@retval EFI_INVALID_PARAMETER Channel is invalid (Channel >= ChannelCount).\r
- @retval EFI_INVALID_PARAMETER Device is invalid. \r
+ @retval EFI_INVALID_PARAMETER Device is invalid.\r
@retval EFI_INVALID_PARAMETER SupportedModes is NULL.\r
- @retval EFI_NOT_READY Modes cannot be calculated due to a lack of \r
- data. This error may happen if \r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData() \r
- and EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyData() \r
- were not called for at least one drive in the \r
+ @retval EFI_NOT_READY Modes cannot be calculated due to a lack of\r
+ data. This error may happen if\r
+ EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData()\r
+ and EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyData()\r
+ were not called for at least one drive in the\r
same enumeration group.\r
\r
**/\r
Commands the IDE controller driver to program the IDE controller hardware\r
so that the specified device can operate at the specified mode.\r
\r
- This function is used by the driver entity to instruct the IDE controller \r
- driver to program the IDE controller hardware to the specified modes. This \r
- function can be called only once for a particular device. For a Serial ATA \r
+ This function is used by the driver entity to instruct the IDE controller\r
+ driver to program the IDE controller hardware to the specified modes. This\r
+ function can be called only once for a particular device. For a Serial ATA\r
(SATA) Advanced Host Controller Interface (AHCI) controller, no controller-\r
specific programming may be required.\r
\r
;\r
\r
/**\r
- This routine is called right after the .Supported() called and \r
+ This routine is called right after the .Supported() called and\r
Start this driver on ControllerHandle.\r
\r
@param This Protocol instance pointer.\r
//\r
/**\r
Returns the information about the specified IDE channel.\r
- \r
+\r
This function can be used to obtain information about a particular IDE channel.\r
- The driver entity uses this information during the enumeration process. \r
- \r
- If Enabled is set to FALSE, the driver entity will not scan the channel. Note \r
+ The driver entity uses this information during the enumeration process.\r
+\r
+ If Enabled is set to FALSE, the driver entity will not scan the channel. Note\r
that it will not prevent an operating system driver from scanning the channel.\r
- \r
- For most of today's controllers, MaxDevices will either be 1 or 2. For SATA \r
- controllers, this value will always be 1. SATA configurations can contain SATA \r
+\r
+ For most of today's controllers, MaxDevices will either be 1 or 2. For SATA\r
+ controllers, this value will always be 1. SATA configurations can contain SATA\r
port multipliers. SATA port multipliers behave like SATA bridges and can support\r
- up to 16 devices on the other side. If a SATA port out of the IDE controller \r
- is connected to a port multiplier, MaxDevices will be set to the number of SATA \r
- devices that the port multiplier supports. Because today's port multipliers \r
- support up to fifteen SATA devices, this number can be as large as fifteen. The IDE \r
- bus driver is required to scan for the presence of port multipliers behind an SATA \r
- controller and enumerate up to MaxDevices number of devices behind the port \r
- multiplier. \r
- \r
- In this context, the devices behind a port multiplier constitute a channel. \r
- \r
+ up to 16 devices on the other side. If a SATA port out of the IDE controller\r
+ is connected to a port multiplier, MaxDevices will be set to the number of SATA\r
+ devices that the port multiplier supports. Because today's port multipliers\r
+ support up to fifteen SATA devices, this number can be as large as fifteen. The IDE\r
+ bus driver is required to scan for the presence of port multipliers behind an SATA\r
+ controller and enumerate up to MaxDevices number of devices behind the port\r
+ multiplier.\r
+\r
+ In this context, the devices behind a port multiplier constitute a channel.\r
+\r
@param[in] This The pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Channel Zero-based channel number.\r
- @param[out] Enabled TRUE if this channel is enabled. Disabled channels \r
+ @param[out] Enabled TRUE if this channel is enabled. Disabled channels\r
are not scanned to see if any devices are present.\r
@param[out] MaxDevices The maximum number of IDE devices that the bus driver\r
- can expect on this channel. For the ATA/ATAPI \r
- specification, version 6, this number will either be \r
- one or two. For Serial ATA (SATA) configurations with a \r
+ can expect on this channel. For the ATA/ATAPI\r
+ specification, version 6, this number will either be\r
+ one or two. For Serial ATA (SATA) configurations with a\r
port multiplier, this number can be as large as fifteen.\r
\r
@retval EFI_SUCCESS Information was returned without any errors.\r
/**\r
The notifications from the driver entity that it is about to enter a certain\r
phase of the IDE channel enumeration process.\r
- \r
- This function can be used to notify the IDE controller driver to perform \r
- specific actions, including any chipset-specific initialization, so that the \r
- chipset is ready to enter the next phase. Seven notification points are defined \r
- at this time. \r
- \r
- More synchronization points may be added as required in the future. \r
+\r
+ This function can be used to notify the IDE controller driver to perform\r
+ specific actions, including any chipset-specific initialization, so that the\r
+ chipset is ready to enter the next phase. Seven notification points are defined\r
+ at this time.\r
+\r
+ More synchronization points may be added as required in the future.\r
\r
@param[in] This The pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Phase The phase during enumeration.\r
@retval EFI_SUCCESS The notification was accepted without any errors.\r
@retval EFI_UNSUPPORTED Phase is not supported.\r
@retval EFI_INVALID_PARAMETER Channel is invalid (Channel >= ChannelCount).\r
- @retval EFI_NOT_READY This phase cannot be entered at this time; for \r
- example, an attempt was made to enter a Phase \r
- without having entered one or more previous \r
+ @retval EFI_NOT_READY This phase cannot be entered at this time; for\r
+ example, an attempt was made to enter a Phase\r
+ without having entered one or more previous\r
Phase.\r
\r
**/\r
/**\r
Submits the device information to the IDE controller driver.\r
\r
- This function is used by the driver entity to pass detailed information about \r
- a particular device to the IDE controller driver. The driver entity obtains \r
+ This function is used by the driver entity to pass detailed information about\r
+ a particular device to the IDE controller driver. The driver entity obtains\r
this information by issuing an ATA or ATAPI IDENTIFY_DEVICE command. IdentifyData\r
- is the pointer to the response data buffer. The IdentifyData buffer is owned \r
- by the driver entity, and the IDE controller driver must make a local copy \r
- of the entire buffer or parts of the buffer as needed. The original IdentifyData \r
+ is the pointer to the response data buffer. The IdentifyData buffer is owned\r
+ by the driver entity, and the IDE controller driver must make a local copy\r
+ of the entire buffer or parts of the buffer as needed. The original IdentifyData\r
buffer pointer may not be valid when\r
- \r
+\r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.CalculateMode() or\r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyMode() is called at a later point.\r
- \r
- The IDE controller driver may consult various fields of EFI_IDENTIFY_DATA to \r
- compute the optimum mode for the device. These fields are not limited to the \r
- timing information. For example, an implementation of the IDE controller driver \r
- may examine the vendor and type/mode field to match known bad drives. \r
- \r
- The driver entity may submit drive information in any order, as long as it \r
- submits information for all the devices belonging to the enumeration group \r
+\r
+ The IDE controller driver may consult various fields of EFI_IDENTIFY_DATA to\r
+ compute the optimum mode for the device. These fields are not limited to the\r
+ timing information. For example, an implementation of the IDE controller driver\r
+ may examine the vendor and type/mode field to match known bad drives.\r
+\r
+ The driver entity may submit drive information in any order, as long as it\r
+ submits information for all the devices belonging to the enumeration group\r
before EFI_IDE_CONTROLLER_INIT_PROTOCOL.CalculateMode() is called for any device\r
in that enumeration group. If a device is absent, EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData()\r
- should be called with IdentifyData set to NULL. The IDE controller driver may \r
- not have any other mechanism to know whether a device is present or not. Therefore, \r
- setting IdentifyData to NULL does not constitute an error condition. \r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData() can be called only once for a \r
- given (Channel, Device) pair. \r
- \r
+ should be called with IdentifyData set to NULL. The IDE controller driver may\r
+ not have any other mechanism to know whether a device is present or not. Therefore,\r
+ setting IdentifyData to NULL does not constitute an error condition.\r
+ EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData() can be called only once for a\r
+ given (Channel, Device) pair.\r
+\r
@param[in] This A pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Channel Zero-based channel number.\r
@param[in] Device Zero-based device number on the Channel.\r
/**\r
Disqualifies specific modes for an IDE device.\r
\r
- This function allows the driver entity or other drivers (such as platform \r
+ This function allows the driver entity or other drivers (such as platform\r
drivers) to reject certain timing modes and request the IDE controller driver\r
- to recalculate modes. This function allows the driver entity and the IDE \r
- controller driver to negotiate the timings on a per-device basis. This function \r
- is useful in the case of drives that lie about their capabilities. An example \r
- is when the IDE device fails to accept the timing modes that are calculated \r
+ to recalculate modes. This function allows the driver entity and the IDE\r
+ controller driver to negotiate the timings on a per-device basis. This function\r
+ is useful in the case of drives that lie about their capabilities. An example\r
+ is when the IDE device fails to accept the timing modes that are calculated\r
by the IDE controller driver based on the response to the Identify Drive command.\r
\r
- If the driver entity does not want to limit the ATA timing modes and leave that \r
- decision to the IDE controller driver, it can either not call this function for \r
- the given device or call this function and set the Valid flag to FALSE for all \r
+ If the driver entity does not want to limit the ATA timing modes and leave that\r
+ decision to the IDE controller driver, it can either not call this function for\r
+ the given device or call this function and set the Valid flag to FALSE for all\r
modes that are listed in EFI_ATA_COLLECTIVE_MODE.\r
- \r
- The driver entity may disqualify modes for a device in any order and any number \r
+\r
+ The driver entity may disqualify modes for a device in any order and any number\r
of times.\r
- \r
- This function can be called multiple times to invalidate multiple modes of the \r
- same type (e.g., Programmed Input/Output [PIO] modes 3 and 4). See the ATA/ATAPI \r
- specification for more information on PIO modes. \r
- \r
+\r
+ This function can be called multiple times to invalidate multiple modes of the\r
+ same type (e.g., Programmed Input/Output [PIO] modes 3 and 4). See the ATA/ATAPI\r
+ specification for more information on PIO modes.\r
+\r
For Serial ATA (SATA) controllers, this member function can be used to disqualify\r
a higher transfer rate mode on a given channel. For example, a platform driver\r
- may inform the IDE controller driver to not use second-generation (Gen2) speeds \r
+ may inform the IDE controller driver to not use second-generation (Gen2) speeds\r
for a certain SATA drive.\r
- \r
+\r
@param[in] This The pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Channel The zero-based channel number.\r
@param[in] Device The zero-based device number on the Channel.\r
@retval EFI_INVALID_PARAMETER Channel is invalid (Channel >= ChannelCount).\r
@retval EFI_INVALID_PARAMETER Device is invalid.\r
@retval EFI_INVALID_PARAMETER IdentifyData is NULL.\r
- \r
+\r
**/\r
EFI_STATUS\r
EFIAPI\r
Returns the information about the optimum modes for the specified IDE device.\r
\r
This function is used by the driver entity to obtain the optimum ATA modes for\r
- a specific device. The IDE controller driver takes into account the following \r
+ a specific device. The IDE controller driver takes into account the following\r
while calculating the mode:\r
- The IdentifyData inputs to EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData()\r
- The BadModes inputs to EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyMode()\r
\r
- The driver entity is required to call EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData() \r
- for all the devices that belong to an enumeration group before calling \r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.CalculateMode() for any device in the same group. \r
- \r
- The IDE controller driver will use controller- and possibly platform-specific \r
- algorithms to arrive at SupportedModes. The IDE controller may base its \r
- decision on user preferences and other considerations as well. This function \r
- may be called multiple times because the driver entity may renegotiate the mode \r
+ The driver entity is required to call EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData()\r
+ for all the devices that belong to an enumeration group before calling\r
+ EFI_IDE_CONTROLLER_INIT_PROTOCOL.CalculateMode() for any device in the same group.\r
+\r
+ The IDE controller driver will use controller- and possibly platform-specific\r
+ algorithms to arrive at SupportedModes. The IDE controller may base its\r
+ decision on user preferences and other considerations as well. This function\r
+ may be called multiple times because the driver entity may renegotiate the mode\r
with the IDE controller driver using EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyMode().\r
- \r
- The driver entity may collect timing information for various devices in any \r
+\r
+ The driver entity may collect timing information for various devices in any\r
order. The driver entity is responsible for making sure that all the dependencies\r
- are satisfied. For example, the SupportedModes information for device A that \r
- was previously returned may become stale after a call to \r
+ are satisfied. For example, the SupportedModes information for device A that\r
+ was previously returned may become stale after a call to\r
EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyMode() for device B.\r
- \r
- The buffer SupportedModes is allocated by the callee because the caller does \r
- not necessarily know the size of the buffer. The type EFI_ATA_COLLECTIVE_MODE \r
- is defined in a way that allows for future extensibility and can be of variable \r
- length. This memory pool should be deallocated by the caller when it is no \r
- longer necessary. \r
- \r
- The IDE controller driver for a Serial ATA (SATA) controller can use this \r
- member function to force a lower speed (first-generation [Gen1] speeds on a \r
- second-generation [Gen2]-capable hardware). The IDE controller driver can \r
- also allow the driver entity to stay with the speed that has been negotiated \r
+\r
+ The buffer SupportedModes is allocated by the callee because the caller does\r
+ not necessarily know the size of the buffer. The type EFI_ATA_COLLECTIVE_MODE\r
+ is defined in a way that allows for future extensibility and can be of variable\r
+ length. This memory pool should be deallocated by the caller when it is no\r
+ longer necessary.\r
+\r
+ The IDE controller driver for a Serial ATA (SATA) controller can use this\r
+ member function to force a lower speed (first-generation [Gen1] speeds on a\r
+ second-generation [Gen2]-capable hardware). The IDE controller driver can\r
+ also allow the driver entity to stay with the speed that has been negotiated\r
by the physical layer.\r
- \r
+\r
@param[in] This The pointer to the EFI_IDE_CONTROLLER_INIT_PROTOCOL instance.\r
@param[in] Channel A zero-based channel number.\r
@param[in] Device A zero-based device number on the Channel.\r
\r
@retval EFI_SUCCESS SupportedModes was returned.\r
@retval EFI_INVALID_PARAMETER Channel is invalid (Channel >= ChannelCount).\r
- @retval EFI_INVALID_PARAMETER Device is invalid. \r
+ @retval EFI_INVALID_PARAMETER Device is invalid.\r
@retval EFI_INVALID_PARAMETER SupportedModes is NULL.\r
- @retval EFI_NOT_READY Modes cannot be calculated due to a lack of \r
- data. This error may happen if \r
- EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData() \r
- and EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyData() \r
- were not called for at least one drive in the \r
+ @retval EFI_NOT_READY Modes cannot be calculated due to a lack of\r
+ data. This error may happen if\r
+ EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData()\r
+ and EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyData()\r
+ were not called for at least one drive in the\r
same enumeration group.\r
\r
**/\r
Commands the IDE controller driver to program the IDE controller hardware\r
so that the specified device can operate at the specified mode.\r
\r
- This function is used by the driver entity to instruct the IDE controller \r
- driver to program the IDE controller hardware to the specified modes. This \r
- function can be called only once for a particular device. For a Serial ATA \r
+ This function is used by the driver entity to instruct the IDE controller\r
+ driver to program the IDE controller hardware to the specified modes. This\r
+ function can be called only once for a particular device. For a Serial ATA\r
(SATA) Advanced Host Controller Interface (AHCI) controller, no controller-\r
specific programming may be required.\r
\r
## @file\r
-# \r
+#\r
# Component description file for the Sata Controller driver.\r
#\r
# Copyright (c) 2011 - 2018, Intel Corporation. All rights reserved.<BR>\r
# SPDX-License-Identifier: BSD-2-Clause-Patent\r
-# \r
+#\r
##\r
\r
[Defines]\r
UefiBootServicesTableLib\r
\r
[Protocols]\r
- gEfiPciIoProtocolGuid \r
+ gEfiPciIoProtocolGuid\r
gEfiIdeControllerInitProtocolGuid\r
\r
//\r
//\r
-// \r
+//\r
EFI_PEI_TEMPORARY_RAM_SUPPORT_PPI mTemporaryRamSupportPpi = {\r
TemporaryRamMigration\r
};\r
0x0, // Reserved_0\r
IA32_IDT_GATE_TYPE_INTERRUPT_32, // GateType\r
0xffff // OffsetHigh\r
- } \r
+ }\r
};\r
\r
/**\r
ASSERT_EFI_ERROR (Status);\r
\r
FindPeiCoreImageBase (BootFirmwareVolumePtr, &PeiCoreImageBase);\r
- \r
+\r
ZeroMem ((VOID *) &ImageContext, sizeof (PE_COFF_LOADER_IMAGE_CONTEXT));\r
//\r
// Report SEC Core debug information when remote debug is enabled\r
\r
//\r
// Initialize IDT\r
- // \r
+ //\r
IdtTableInStack.PeiService = NULL;\r
for (Index = 0; Index < SEC_IDT_ENTRY_COUNT; Index ++) {\r
CopyMem (&IdtTableInStack.IdtTable[Index], &mIdtEntryTemplate, sizeof (mIdtEntryTemplate));\r
//\r
InitializeApicTimer (0, MAX_UINT32, TRUE, 5);\r
DisableApicTimerInterrupt ();\r
- \r
+\r
//\r
// Initialize Debug Agent to support source level debug in SEC/PEI phases before memory ready.\r
//\r
InitializeDebugAgent (DEBUG_AGENT_INIT_PREMEM_SEC, &SecCoreData, SecStartupPhase2);\r
}\r
- \r
+\r
/**\r
Caller provided function to be invoked at the end of InitializeDebugAgent().\r
\r
EFI_SEC_PEI_HAND_OFF *SecCoreData;\r
EFI_FIRMWARE_VOLUME_HEADER *BootFv;\r
EFI_PEI_CORE_ENTRY_POINT PeiCoreEntryPoint;\r
- \r
+\r
SecCoreData = (EFI_SEC_PEI_HAND_OFF *) Context;\r
- \r
+\r
//\r
// Find PEI Core entry point. It will report SEC and Pei Core debug information if remote debug\r
// is enabled.\r
// Transfer the control to the PEI core\r
//\r
(*PeiCoreEntryPoint) (SecCoreData, (EFI_PEI_PPI_DESCRIPTOR *)&mPrivateDispatchTable);\r
- \r
+\r
//\r
// If we get here then the PEI Core returned, which is not recoverable.\r
//\r
DEBUG_AGENT_CONTEXT_POSTMEM_SEC DebugAgentContext;\r
BOOLEAN OldStatus;\r
BASE_LIBRARY_JUMP_BUFFER JumpBuffer;\r
- \r
+\r
DEBUG ((EFI_D_INFO,\r
"TemporaryRamMigration(0x%Lx, 0x%Lx, 0x%Lx)\n",\r
TemporaryMemoryBase,\r
PermanentMemoryBase,\r
(UINT64)CopySize\r
));\r
- \r
+\r
OldHeap = (VOID*)(UINTN)TemporaryMemoryBase;\r
NewHeap = (VOID*)((UINTN)PermanentMemoryBase + (CopySize >> 1));\r
- \r
+\r
OldStack = (VOID*)((UINTN)TemporaryMemoryBase + (CopySize >> 1));\r
NewStack = (VOID*)(UINTN)PermanentMemoryBase;\r
\r
DebugAgentContext.HeapMigrateOffset = (UINTN)NewHeap - (UINTN)OldHeap;\r
DebugAgentContext.StackMigrateOffset = (UINTN)NewStack - (UINTN)OldStack;\r
- \r
+\r
OldStatus = SaveAndSetDebugTimerInterrupt (FALSE);\r
InitializeDebugAgent (DEBUG_AGENT_INIT_POSTMEM_SEC, (VOID *) &DebugAgentContext, NULL);\r
\r
// Migrate Stack\r
//\r
CopyMem (NewStack, OldStack, CopySize >> 1);\r
- \r
+\r
//\r
// Rebase IDT table in permanent memory\r
//\r
\r
//\r
// Use SetJump()/LongJump() to switch to a new stack.\r
- // \r
+ //\r
if (SetJump (&JumpBuffer) == 0) {\r
#if defined (MDE_CPU_IA32)\r
JumpBuffer.Esp = JumpBuffer.Esp + DebugAgentContext.StackMigrateOffset;\r
JumpBuffer.Ebp = JumpBuffer.Ebp + DebugAgentContext.StackMigrateOffset;\r
-#endif \r
+#endif\r
#if defined (MDE_CPU_X64)\r
JumpBuffer.Rsp = JumpBuffer.Rsp + DebugAgentContext.StackMigrateOffset;\r
JumpBuffer.Rbp = JumpBuffer.Rbp + DebugAgentContext.StackMigrateOffset;\r
-#endif \r
+#endif\r
LongJump (&JumpBuffer, (UINTN)-1);\r
}\r
\r
projects / mirror_edk2.git / commitdiff