\r
@param CallerId This optional parameter may be used to identify the caller. \r
This parameter allows the status code driver to apply different rules to different callers. \r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
}\r
//\r
// The length of the field 'Position Set Code Length Array Size' in Block Header.\r
- // For EFI 1.1 de/compression algorithm(Version 1), mPBit = 4\r
+ // For UEFI 2.0 de/compression algorithm(Version 1), mPBit = 4\r
// For Tiano de/compression algorithm(Version 2), mPBit = 5\r
//\r
switch (Version) {\r
\r
//\r
// The length of the field 'Position Set Code Length Array Size' in Block Header.\r
- // For EFI 1.1 de/compression algorithm, mPBit = 4\r
+ // For UEFI 2.0 de/compression algorithm, mPBit = 4\r
// For Tiano de/compression algorithm, mPBit = 5\r
//\r
UINT8 mPBit;\r
\r
@param CallerId This optional parameter may be used to identify the caller. \r
This parameter allows the status code driver to apply different rules to different callers. \r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
\r
@param CallerId This optional parameter may be used to identify the caller.\r
This parameter allows the status code driver to apply different rules to different callers.\r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
\r
@param CallerId This optional parameter may be used to identify the caller.\r
This parameter allows the status code driver to apply different rules to different callers.\r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
\r
@param CallerId This optional parameter may be used to identify the caller.\r
This parameter allows the status code driver to apply different rules to different callers.\r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
\r
@param CallerId This optional parameter may be used to identify the caller. \r
This parameter allows the status code driver to apply different rules to different callers. \r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
\r
@param CallerId This optional parameter may be used to identify the caller.\r
This parameter allows the status code driver to apply different rules to different callers.\r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
\r
@param CallerId This optional parameter may be used to identify the caller.\r
This parameter allows the status code driver to apply different rules to different callers.\r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
/** @file\r
- Include file that supportes Framework extension to the EFI 1.10 spec.\r
+ Include file that supportes Framework extension to the UEFI 2.0 spec.\r
\r
This include file must only contain things defined in the Framework\r
specifications. If a code construct is defined in the Framework specification\r
EFI_RESET_SYSTEM ResetSystem;\r
\r
//\r
- // Framework extension to EFI 1.10 runtime table\r
+ // Framework extension to UEFI 2.0 runtime table\r
// It was moved to a protocol to not conflict with UEFI 2.0\r
//\r
EFI_REPORT_STATUS_CODE ReportStatusCode;\r
The GetPciRom() function gets the PCI device's option ROM from a platform-specific location.\r
The option ROM will be loaded into memory. This member function is used to return an image\r
that is packaged as a PCI 2.2 option ROM. The image may contain both legacy and EFI option\r
- ROMs. See the EFI 1.10 Specification for details. This member function can be used to return\r
+ ROMs. See the UEFI 2.0 Specification for details. This member function can be used to return\r
option ROM images for embedded controllers. Option ROMs for embedded controllers are typically\r
stored in platform-specific storage, and this member function can retrieve it from that storage\r
and return it to the PCI bus driver. The PCI bus driver will call this member function before\r
DriverEntry->DepexProtocolError = TRUE;\r
} else {\r
//\r
- // If no Depex assume EFI 1.1 driver model\r
+ // If no Depex assume UEFI 2.0 driver model\r
//\r
DriverEntry->Depex = NULL;\r
DriverEntry->Dependent = TRUE;\r
\r
if (DriverEntry->Depex == NULL) {\r
//\r
- // A NULL Depex means treat the driver like an EFI 1.0 thing.\r
+ // A NULL Depex means treat the driver like an UEFI 2.0 thing.\r
//\r
Status = CoreAllEfiServicesAvailable ();\r
if (EFI_ERROR (Status)) {\r
\r
Routine Description:\r
\r
- EFI 1.0 API to terminate Boot Services\r
+ UEFI 2.0 API to terminate Boot Services\r
\r
Arguments:\r
\r
Function = NotifyFunction;\r
\r
//\r
- // Convert EFI 1.10 Events to thier UEFI 2.0 CreateEventEx mapping\r
+ // Convert EFI 1.10 Events to their UEFI 2.0 CreateEventEx mapping\r
//\r
if (Type == EVT_SIGNAL_EXIT_BOOT_SERVICES) {\r
GuidPtr = &gEfiEventExitBootServicesGuid;\r
LoadPe32Image.h\r
\r
Abstract:\r
- Load File protocol as defined in the EFI 1.0 specification.\r
+ Load File protocol.\r
\r
Load file protocol exists to supports the addition of new boot devices,\r
and to support booting from devices that do not map well to file system.\r
Network boot is done via a LoadFile protocol.\r
\r
- EFI 1.0 can boot from any device that produces a LoadFile protocol.\r
+ UEFI 2.0 can boot from any device that produces a LoadFile protocol.\r
\r
--*/\r
\r
/**@file\r
This is the main routine for initializing the Graphics Console support routines.\r
Remaining Tasks\r
- Add all standard Glyphs from EFI 1.02 Specification\r
+ Add all standard Glyphs from UEFI 2.0 Specification\r
Implement optimal automatic Mode creation algorithm\r
Solve palette issues for mixed graphics and text\r
When does this protocol reset the palette?\r
^ = CTRL\r
\r
+=========+======+===========+==========+==========+\r
-| | EFI | EFI 1.10 | | |\r
+| | EFI | UEFI 2.0 | | |\r
| | Scan | | VT100+ | |\r
| KEY | Code | PC ANSI | VTUTF8 | VT100 |\r
+=========+======+===========+==========+==========+\r
EFI_UNSUPPORTED\r
\r
Arguments:\r
- Per EFI 1.10 driver model\r
+ Per UEFI 2.0 driver model\r
\r
Returns:\r
EFI_UNSUPPORTED\r
/** @file\r
- Decode a hard disk partitioned with the GPT scheme in the EFI 1.0\r
+ Decode a hard disk partitioned with the GPT scheme in the UEFI 2.0\r
specification.\r
\r
Copyright (c) 2006 - 2007, Intel Corporation \r
/** @file\r
- SimpleFileSystem guid and data structure as defined in the EFI 1.0 specification.\r
+ SimpleFileSystem guid and data structure as defined in the UEFI 2.0 specification.\r
\r
The SimpleFileSystem protocol is the programatic access to the FAT (12,16,32) \r
- file system specified in EFI 1.0. It can also be used to abstract any \r
+ file system specified in UEFI 2.0. It can also be used to abstract any \r
file system other than FAT.\r
\r
- EFI 1.0 can boot from any valid EFI image contained in a SimpleFileSystem\r
+ UEFI 2.0 can boot from any valid EFI image contained in a SimpleFileSystem\r
\r
Copyright (c) 2006, Intel Corporation \r
All rights reserved. This program and the accompanying materials \r
/** @file\r
- FileSystemInfo guid and data structure as defined in the EFI 1.0 specification.\r
+ FileSystemInfo guid and data structure as defined in the UEFI 2.0 specification.\r
\r
Copyright (c) 2006, Intel Corporation \r
All rights reserved. This program and the accompanying materials \r
/** @file\r
- FileSystemVolumeLabelInfo guid and data structure as defined in the EFI 1.0 specification.\r
+ FileSystemVolumeLabelInfo guid and data structure as defined in the UEFI 2.0 specification.\r
\r
Copyright (c) 2006, Intel Corporation \r
All rights reserved. This program and the accompanying materials \r
/** @file\r
- GUIDs used for MPS entries in the EFI 1.0 system table\r
+ GUIDs used for MPS entries in the UEFI 2.0 system table\r
ACPI is the primary means of exporting MP information to the OS. MPS obly was\r
included to support Itanium-based platform power on. So don't use it if you don't have too.\r
\r
/** @file\r
- GUIDs used to locate the SMBIOS tables in the EFI 1.0 system table.\r
+ GUIDs used to locate the SMBIOS tables in the UEFI 2.0 system table.\r
\r
This GUID in the system table is the only legal way to search for and \r
locate the SMBIOS tables. Do not search the 0xF0000 segment to find SMBIOS\r
/** @file\r
- Block IO protocol as defined in the EFI 1.0 specification.\r
+ Block IO protocol as defined in the UEFI 2.0 specification.\r
\r
The Block IO protocol is used to abstract block devices like hard drives,\r
DVD-ROMs and floppy drives.\r
/** @file\r
- Bus Specific Driver Override protocol as defined in the EFI 1.1 specification.\r
+ Bus Specific Driver Override protocol as defined in the UEFI 2.0 specification.\r
\r
Copyright (c) 2006, Intel Corporation \r
All rights reserved. This program and the accompanying materials \r
/** @file\r
- Device IO protocol as defined in the EFI 1.0 specification.\r
+ Device IO protocol as defined in the EFI 1.10 specification.\r
\r
Device IO is used to abstract hardware access to devices. It includes\r
memory mapped IO, IO, PCI Config space, and DMA.\r
/** @file\r
- The device path protocol as defined in EFI 1.0.\r
+ The device path protocol as defined in UEFI 2.0.\r
\r
The device path represents a programatic path to a device. It's the view\r
from a software point of view. It also must persist from boot to boot, so \r
/** @file\r
- Disk IO protocol as defined in the EFI 1.0 specification.\r
+ Disk IO protocol as defined in the UEFI 2.0 specification.\r
\r
The Disk IO protocol is used to convert block oriented devices into byte\r
oriented devices. The Disk IO protocol is intended to layer on top of the\r
#include <Protocol/DriverConfiguration2.h>\r
\r
//\r
-// Global ID for the Driver Configuration Protocol defined in EFI 1.10\r
+// Global ID for the Driver Configuration Protocol defined in UEFI 2.0\r
//\r
#define EFI_DRIVER_CONFIGURATION_PROTOCOL_GUID \\r
{ \\r
#define __EFI_DRIVER_DIAGNOSTICS_H__\r
\r
//\r
-// Global ID for the Driver Diagnostics Protocol as defined in EFI 1.10.\r
+// Global ID for the Driver Diagnostics Protocol as defined in UEFI 2.0.\r
//\r
#define EFI_DRIVER_DIAGNOSTICS_PROTOCOL_GUID \\r
{ \\r
/** @file\r
- Load File protocol as defined in the EFI 1.0 specification.\r
+ Load File protocol as defined in the UEFI 2.0 specification.\r
\r
Load file protocol exists to supports the addition of new boot devices, \r
and to support booting from devices that do not map well to file system. \r
Network boot is done via a LoadFile protocol.\r
\r
- EFI 1.0 can boot from any device that produces a LoadFile protocol.\r
+ UEFI 2.0 can boot from any device that produces a LoadFile protocol.\r
\r
Copyright (c) 2006, Intel Corporation \r
All rights reserved. This program and the accompanying materials \r
/** @file\r
- EFI 1.0 Loaded image protocol definition.\r
+ UEFI 2.0 Loaded image protocol definition.\r
\r
Every EFI driver and application is passed an image handle when it is loaded.\r
This image handle will contain a Loaded Image Protocol.\r
/** @file\r
- PCI Root Bridge I/O protocol as defined in the EFI 1.1 specification.\r
+ PCI Root Bridge I/O protocol as defined in the UEFI 2.0 specification.\r
\r
PCI Root Bridge I/O protocol is used by PCI Bus Driver to perform PCI Memory, PCI I/O, \r
and PCI Configuration cycles on a PCI Root Bridge. It also provides services to perform \r
/** @file\r
- Platform Driver Override protocol as defined in the EFI 1.1 specification.\r
+ Platform Driver Override protocol as defined in the UEFI 2.1 specification.\r
\r
Copyright (c) 2006, Intel Corporation \r
All rights reserved. This program and the accompanying materials \r
This code abstracts time and data functions. Used to provide\r
Time and date related EFI runtime services.\r
\r
- The GetTime (), SetTime (), GetWakeupTime (), and SetWakeupTime () EFI 1.0\r
+ The GetTime (), SetTime (), GetWakeupTime (), and SetWakeupTime () UEFI 2.0\r
services are added to the EFI system table and the \r
EFI_REAL_TIME_CLOCK_ARCH_PROTOCOL_GUID protocol is registered with a NULL \r
pointer.\r
\r
Used to provide ResetSystem runtime services\r
\r
- The ResetSystem () EFI 1.0 service is added to the EFI system table and the \r
+ The ResetSystem () UEFI 2.0 service is added to the EFI system table and the \r
EFI_RESET_ARCH_PROTOCOL_GUID protocol is registered with a NULL pointer.\r
\r
No CRC of the EFI system table is required, as it is done in the DXE core.\r
/** @file\r
Runtime Architectural Protocol as defined in DXE CIS\r
\r
- This code is used to produce the EFI 1.0 runtime virtual switch over\r
+ This code is used to produce the UEFI 2.0 runtime virtual switch over\r
\r
This driver must add SetVirtualAddressMap () and ConvertPointer () to\r
the EFI system table. This driver is not responcible for CRCing the \r
/** @file\r
- Serial IO protocol as defined in the EFI 1.0 specification.\r
+ Serial IO protocol as defined in the UEFI 2.0 specification.\r
\r
Abstraction of a basic serial device. Targeted at 16550 UART, but\r
could be much more generic.\r
/** @file\r
- SimpleFileSystem protocol as defined in the EFI 1.0 specification.\r
+ SimpleFileSystem protocol as defined in the UEFI 2.0 specification.\r
\r
The SimpleFileSystem protocol is the programatic access to the FAT (12,16,32) \r
- file system specified in EFI 1.0. It can also be used to abstract a file \r
+ file system specified in UEFI 2.0. It can also be used to abstract a file \r
system other than FAT.\r
\r
- EFI 1.0 can boot from any valid EFI image contained in a SimpleFileSystem\r
+ UEFI 2.0 can boot from any valid EFI image contained in a SimpleFileSystem\r
\r
Copyright (c) 2006, Intel Corporation \r
All rights reserved. This program and the accompanying materials \r
/** @file\r
- Simple Network protocol as defined in the EFI 1.0 specification.\r
+ Simple Network protocol as defined in the UEFI 2.0 specification.\r
\r
Basic network device abstraction.\r
\r
/** @file\r
- Simple Pointer protocol from the EFI 1.1 specification.\r
+ Simple Pointer protocol from the UEFI 2.0 specification.\r
\r
Abstraction of a very simple pointer device like a mice or tracekballs.\r
\r
/** @file\r
- Simple Text In protocol from the EFI 1.0 specification.\r
+ Simple Text In protocol from the UEFI 2.0 specification.\r
\r
Abstraction of a very simple input device like a keyboard or serial\r
terminal.\r
/** @file\r
- Simple Text Out protocol from the EFI 1.0 specification.\r
+ Simple Text Out protocol from the UEFI 2.0 specification.\r
\r
Abstraction of a very simple text based output device like VGA text mode or\r
a serial terminal. The Simple Text Out protocol instance can represent\r
/** @file\r
- UGA Draw protocol from the EFI 1.1 specification.\r
+ UGA Draw protocol from the EFI 1.10 specification.\r
\r
Abstraction of a very simple graphics device.\r
\r
/** @file\r
- UGA IO protocol from the EFI 1.1 specification.\r
+ UGA IO protocol from the EFI 1.10 specification.\r
\r
Abstraction of a very simple graphics device.\r
\r
/** @file\r
- Unicode Collation protocol that follows the EFI 1.0 specification.\r
+ Unicode Collation protocol that follows the UEFI 2.0 specification.\r
\r
Copyright (c) 2006, Intel Corporation \r
All rights reserved. This program and the accompanying materials \r
/** @file\r
Variable Architectural Protocol as defined in the DXE CIS\r
\r
- This code is used to produce the EFI 1.0 runtime variable services\r
+ This code is used to produce the UEFI 2.0 runtime variable services\r
\r
- The GetVariable (), GetNextVariableName (), and SetVariable () EFI 1.0 \r
+ The GetVariable (), GetNextVariableName (), and SetVariable () UEFI 2.0 \r
services are added to the EFI system table and the \r
EFI_VARIABLE_ARCH_PROTOCOL_GUID protocol is registered with a NULL pointer.\r
\r
/** @file\r
Variable Write Architectural Protocol as defined in the DXE CIS\r
\r
- This code is used to produce the EFI 1.0 runtime variable services\r
+ This code is used to produce the UEFI 2.0 runtime variable services\r
\r
- The SetVariable () EFI 1.0 services may be updated to the EFI system table and the \r
+ The SetVariable () UEFI 2.0 services may be updated to the EFI system table and the \r
EFI_VARIABLE_WRITE_ARCH_PROTOCOL_GUID protocol is registered with a NULL pointer.\r
\r
No CRC of the EFI system table is required, as it is done in the DXE core.\r
\r
case EFI_IMAGE_REL_BASED_HIGHADJ:\r
//\r
- // Not implemented, but not used in EFI 1.0\r
+ // Not implemented, but not used in UEFI 2.0\r
//\r
ASSERT (FALSE);\r
break;\r
}\r
//\r
// The length of the field 'Position Set Code Length Array Size' in Block Header.\r
- // For EFI 1.1 de/compression algorithm(Version 1), mPBit = 4\r
+ // For UEFI 2.0 de/compression algorithm(Version 1), mPBit = 4\r
// For Tiano de/compression algorithm(Version 2), mPBit = 5\r
//\r
Sd->mPBit = 4;\r
\r
///\r
/// The length of the field 'Position Set Code Length Array Size' in Block Header.\r
- /// For EFI 1.1 de/compression algorithm, mPBit = 4\r
+ /// For UEFI 2.0 de/compression algorithm, mPBit = 4\r
/// For Tiano de/compression algorithm, mPBit = 5\r
///\r
UINT8 mPBit;\r
\r
@param CallerId This optional parameter may be used to identify the caller.\r
This parameter allows the status code driver to apply different rules to different callers.\r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
\r
Routine Description:\r
\r
- Process the boot option follow the EFI 1.1 specification and\r
+ Process the boot option follow the UEFI 2.0 specification and\r
special treat the legacy boot option with BBS_DEVICE_PATH.\r
\r
Arguments:\r
BdsLibRegisterNewOption (&TempBootLists, DevicePath, L"EFI Internal Shell", L"BootOrder"); \r
}\r
\r
- DEBUG ((EFI_D_INFO | EFI_D_LOAD, "Booting EFI 1.1 way %S\n", Option->Description));\r
+ DEBUG ((EFI_D_INFO | EFI_D_LOAD, "Booting UEFI 2.0 way %S\n", Option->Description));\r
\r
Status = gBS->LoadImage (\r
TRUE,\r
\r
do {\r
//\r
- // Connect All EFI 1.10 drivers following EFI 1.10 algorithm\r
+ // Connect All UEFI 2.0 drivers following UEFI 2.0 algorithm\r
//\r
BdsLibConnectAllEfi ();\r
\r
\r
@param CallerId This optional parameter may be used to identify the caller.\r
This parameter allows the status code driver to apply different rules to different callers.\r
- Type EFI_GUID is defined in InstallProtocolInterface() in the EFI 1.10 Specification.\r
+ Type EFI_GUID is defined in InstallProtocolInterface() in the UEFI 2.0 Specification.\r
\r
\r
@param Data This optional parameter may be used to pass additional data\r
Routine Description:\r
\r
Hook point after a boot attempt succeeds. We don't expect a boot option to\r
- return, so the EFI 1.0 specification defines that you will default to an\r
+ return, so the UEFI 2.0 specification defines that you will default to an\r
interactive mode and stop processing the BootOrder list in this case. This\r
is alos a platform implementation and can be customized by IBV/OEM.\r
\r
PlatformBdsInit (PrivateData);\r
\r
//\r
- // Set up the device list based on EFI 1.1 variables\r
+ // Set up the device list based on UEFI 2.0 variables\r
// process Driver#### and Load the driver's in the\r
// driver option list\r
//\r
;\r
\r
//\r
-// EFI 1.1 driver model prototypes for Win NT GOP\r
+// UEFI 2.0 driver model prototypes for Win NT GOP\r
//\r
\r
\r
Abstract:\r
\r
This file produces the graphics abstration of GOP. It is called by\r
- WinNtGopDriver.c file which deals with the EFI 1.1 driver model.\r
+ WinNtGopDriver.c file which deals with the UEFI 2.0 driver model.\r
This file just does graphics.\r
\r
\r
projects / mirror_edk2.git / commitdiff