Clean up: update "EFI" to "UEFI" if applicable.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@4317 6f19259b-4bc3-4df7-8a09-765794883524
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Block IO protocol as defined in the EFI 1.0 specification.
|
||||
Block IO protocol as defined in the UEFI 2.0 specification.
|
||||
|
||||
The Block IO protocol is used to abstract block devices like hard drives,
|
||||
DVD-ROMs and floppy drives.
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Bus Specific Driver Override protocol as defined in the EFI 1.1 specification.
|
||||
Bus Specific Driver Override protocol as defined in the UEFI 2.0 specification.
|
||||
|
||||
Copyright (c) 2006, Intel Corporation
|
||||
All rights reserved. This program and the accompanying materials
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Device IO protocol as defined in the EFI 1.0 specification.
|
||||
Device IO protocol as defined in the EFI 1.10 specification.
|
||||
|
||||
Device IO is used to abstract hardware access to devices. It includes
|
||||
memory mapped IO, IO, PCI Config space, and DMA.
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
The device path protocol as defined in EFI 1.0.
|
||||
The device path protocol as defined in UEFI 2.0.
|
||||
|
||||
The device path represents a programatic path to a device. It's the view
|
||||
from a software point of view. It also must persist from boot to boot, so
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Disk IO protocol as defined in the EFI 1.0 specification.
|
||||
Disk IO protocol as defined in the UEFI 2.0 specification.
|
||||
|
||||
The Disk IO protocol is used to convert block oriented devices into byte
|
||||
oriented devices. The Disk IO protocol is intended to layer on top of the
|
||||
|
@@ -18,7 +18,7 @@
|
||||
#include <Protocol/DriverConfiguration2.h>
|
||||
|
||||
//
|
||||
// Global ID for the Driver Configuration Protocol defined in EFI 1.10
|
||||
// Global ID for the Driver Configuration Protocol defined in UEFI 2.0
|
||||
//
|
||||
#define EFI_DRIVER_CONFIGURATION_PROTOCOL_GUID \
|
||||
{ \
|
||||
|
@@ -16,7 +16,7 @@
|
||||
#define __EFI_DRIVER_DIAGNOSTICS_H__
|
||||
|
||||
//
|
||||
// Global ID for the Driver Diagnostics Protocol as defined in EFI 1.10.
|
||||
// Global ID for the Driver Diagnostics Protocol as defined in UEFI 2.0.
|
||||
//
|
||||
#define EFI_DRIVER_DIAGNOSTICS_PROTOCOL_GUID \
|
||||
{ \
|
||||
|
@@ -1,11 +1,11 @@
|
||||
/** @file
|
||||
Load File protocol as defined in the EFI 1.0 specification.
|
||||
Load File protocol as defined in the UEFI 2.0 specification.
|
||||
|
||||
Load file protocol exists to supports the addition of new boot devices,
|
||||
and to support booting from devices that do not map well to file system.
|
||||
Network boot is done via a LoadFile protocol.
|
||||
|
||||
EFI 1.0 can boot from any device that produces a LoadFile protocol.
|
||||
UEFI 2.0 can boot from any device that produces a LoadFile protocol.
|
||||
|
||||
Copyright (c) 2006, Intel Corporation
|
||||
All rights reserved. This program and the accompanying materials
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
EFI 1.0 Loaded image protocol definition.
|
||||
UEFI 2.0 Loaded image protocol definition.
|
||||
|
||||
Every EFI driver and application is passed an image handle when it is loaded.
|
||||
This image handle will contain a Loaded Image Protocol.
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
PCI Root Bridge I/O protocol as defined in the EFI 1.1 specification.
|
||||
PCI Root Bridge I/O protocol as defined in the UEFI 2.0 specification.
|
||||
|
||||
PCI Root Bridge I/O protocol is used by PCI Bus Driver to perform PCI Memory, PCI I/O,
|
||||
and PCI Configuration cycles on a PCI Root Bridge. It also provides services to perform
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Platform Driver Override protocol as defined in the EFI 1.1 specification.
|
||||
Platform Driver Override protocol as defined in the UEFI 2.1 specification.
|
||||
|
||||
Copyright (c) 2006, Intel Corporation
|
||||
All rights reserved. This program and the accompanying materials
|
||||
|
@@ -4,7 +4,7 @@
|
||||
This code abstracts time and data functions. Used to provide
|
||||
Time and date related EFI runtime services.
|
||||
|
||||
The GetTime (), SetTime (), GetWakeupTime (), and SetWakeupTime () EFI 1.0
|
||||
The GetTime (), SetTime (), GetWakeupTime (), and SetWakeupTime () UEFI 2.0
|
||||
services are added to the EFI system table and the
|
||||
EFI_REAL_TIME_CLOCK_ARCH_PROTOCOL_GUID protocol is registered with a NULL
|
||||
pointer.
|
||||
|
@@ -3,7 +3,7 @@
|
||||
|
||||
Used to provide ResetSystem runtime services
|
||||
|
||||
The ResetSystem () EFI 1.0 service is added to the EFI system table and the
|
||||
The ResetSystem () UEFI 2.0 service is added to the EFI system table and the
|
||||
EFI_RESET_ARCH_PROTOCOL_GUID protocol is registered with a NULL pointer.
|
||||
|
||||
No CRC of the EFI system table is required, as it is done in the DXE core.
|
||||
|
@@ -1,7 +1,7 @@
|
||||
/** @file
|
||||
Runtime Architectural Protocol as defined in DXE CIS
|
||||
|
||||
This code is used to produce the EFI 1.0 runtime virtual switch over
|
||||
This code is used to produce the UEFI 2.0 runtime virtual switch over
|
||||
|
||||
This driver must add SetVirtualAddressMap () and ConvertPointer () to
|
||||
the EFI system table. This driver is not responcible for CRCing the
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Serial IO protocol as defined in the EFI 1.0 specification.
|
||||
Serial IO protocol as defined in the UEFI 2.0 specification.
|
||||
|
||||
Abstraction of a basic serial device. Targeted at 16550 UART, but
|
||||
could be much more generic.
|
||||
|
@@ -1,11 +1,11 @@
|
||||
/** @file
|
||||
SimpleFileSystem protocol as defined in the EFI 1.0 specification.
|
||||
SimpleFileSystem protocol as defined in the UEFI 2.0 specification.
|
||||
|
||||
The SimpleFileSystem protocol is the programatic access to the FAT (12,16,32)
|
||||
file system specified in EFI 1.0. It can also be used to abstract a file
|
||||
file system specified in UEFI 2.0. It can also be used to abstract a file
|
||||
system other than FAT.
|
||||
|
||||
EFI 1.0 can boot from any valid EFI image contained in a SimpleFileSystem
|
||||
UEFI 2.0 can boot from any valid EFI image contained in a SimpleFileSystem
|
||||
|
||||
Copyright (c) 2006, Intel Corporation
|
||||
All rights reserved. This program and the accompanying materials
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Simple Network protocol as defined in the EFI 1.0 specification.
|
||||
Simple Network protocol as defined in the UEFI 2.0 specification.
|
||||
|
||||
Basic network device abstraction.
|
||||
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Simple Pointer protocol from the EFI 1.1 specification.
|
||||
Simple Pointer protocol from the UEFI 2.0 specification.
|
||||
|
||||
Abstraction of a very simple pointer device like a mice or tracekballs.
|
||||
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Simple Text In protocol from the EFI 1.0 specification.
|
||||
Simple Text In protocol from the UEFI 2.0 specification.
|
||||
|
||||
Abstraction of a very simple input device like a keyboard or serial
|
||||
terminal.
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Simple Text Out protocol from the EFI 1.0 specification.
|
||||
Simple Text Out protocol from the UEFI 2.0 specification.
|
||||
|
||||
Abstraction of a very simple text based output device like VGA text mode or
|
||||
a serial terminal. The Simple Text Out protocol instance can represent
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
UGA Draw protocol from the EFI 1.1 specification.
|
||||
UGA Draw protocol from the EFI 1.10 specification.
|
||||
|
||||
Abstraction of a very simple graphics device.
|
||||
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
UGA IO protocol from the EFI 1.1 specification.
|
||||
UGA IO protocol from the EFI 1.10 specification.
|
||||
|
||||
Abstraction of a very simple graphics device.
|
||||
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/** @file
|
||||
Unicode Collation protocol that follows the EFI 1.0 specification.
|
||||
Unicode Collation protocol that follows the UEFI 2.0 specification.
|
||||
|
||||
Copyright (c) 2006, Intel Corporation
|
||||
All rights reserved. This program and the accompanying materials
|
||||
|
@@ -1,9 +1,9 @@
|
||||
/** @file
|
||||
Variable Architectural Protocol as defined in the DXE CIS
|
||||
|
||||
This code is used to produce the EFI 1.0 runtime variable services
|
||||
This code is used to produce the UEFI 2.0 runtime variable services
|
||||
|
||||
The GetVariable (), GetNextVariableName (), and SetVariable () EFI 1.0
|
||||
The GetVariable (), GetNextVariableName (), and SetVariable () UEFI 2.0
|
||||
services are added to the EFI system table and the
|
||||
EFI_VARIABLE_ARCH_PROTOCOL_GUID protocol is registered with a NULL pointer.
|
||||
|
||||
|
@@ -1,9 +1,9 @@
|
||||
/** @file
|
||||
Variable Write Architectural Protocol as defined in the DXE CIS
|
||||
|
||||
This code is used to produce the EFI 1.0 runtime variable services
|
||||
This code is used to produce the UEFI 2.0 runtime variable services
|
||||
|
||||
The SetVariable () EFI 1.0 services may be updated to the EFI system table and the
|
||||
The SetVariable () UEFI 2.0 services may be updated to the EFI system table and the
|
||||
EFI_VARIABLE_WRITE_ARCH_PROTOCOL_GUID protocol is registered with a NULL pointer.
|
||||
|
||||
No CRC of the EFI system table is required, as it is done in the DXE core.
|
||||
|
Reference in New Issue
Block a user