(EDK/EFI 1.10) and new (EDK II/UEFI 2.0) way. This module is a DXE driver as\r
it contains DXE enum extensions for EFI event services.\r
\r
-Copyright (c) 2006 - 2008, Intel Corporation. All rights reserved.<BR>\r
+Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>\r
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
{\r
return EfiCreateEventLegacyBootEx (\r
TPL_CALLBACK,\r
- InternalEmptyFunction,\r
+ EfiEventEmptyFunction,\r
NULL,\r
LegacyBootEvent\r
);\r
\r
/**\r
Create an EFI event in the Legacy Boot Event Group and allows\r
- the caller to specify a notification function. \r
- \r
+ the caller to specify a notification function.\r
+\r
This function abstracts the creation of the Legacy Boot Event.\r
The Framework moved from a proprietary to UEFI 2.0 based mechanism.\r
This library abstracts the caller from how this event is created to prevent\r
// CreateEventEx will check NotifyFunction is NULL or not and return error.\r
// Use dummy routine for the case NotifyFunction is NULL.\r
//\r
- WorkerNotifyFunction = InternalEmptyFunction;\r
+ WorkerNotifyFunction = EfiEventEmptyFunction;\r
} else {\r
WorkerNotifyFunction = NotifyFunction;\r
}\r
Create an EFI event in the Ready To Boot Event Group.\r
\r
Prior to UEFI 2.0 this was done via a non-standard UEFI extension, and this library\r
- abstracts the implementation mechanism of this event from the caller. \r
- This function abstracts the creation of the Ready to Boot Event. The Framework \r
- moved from a proprietary to UEFI 2.0-based mechanism. This library abstracts \r
- the caller from how this event is created to prevent the code form having to \r
+ abstracts the implementation mechanism of this event from the caller.\r
+ This function abstracts the creation of the Ready to Boot Event. The Framework\r
+ moved from a proprietary to UEFI 2.0-based mechanism. This library abstracts\r
+ the caller from how this event is created to prevent the code form having to\r
change with the version of the specification supported.\r
If ReadyToBootEvent is NULL, then ASSERT().\r
\r
{\r
return EfiCreateEventReadyToBootEx (\r
TPL_CALLBACK,\r
- InternalEmptyFunction,\r
+ EfiEventEmptyFunction,\r
NULL,\r
ReadyToBootEvent\r
);\r
\r
/**\r
Create an EFI event in the Ready To Boot Event Group and allows\r
- the caller to specify a notification function. \r
- \r
+ the caller to specify a notification function.\r
+\r
This function abstracts the creation of the Ready to Boot Event.\r
The Framework moved from a proprietary to UEFI 2.0 based mechanism.\r
This library abstracts the caller from how this event is created to prevent\r
// CreateEventEx will check NotifyFunction is NULL or not and return error.\r
// Use dummy routine for the case NotifyFunction is NULL.\r
//\r
- WorkerNotifyFunction = InternalEmptyFunction;\r
+ WorkerNotifyFunction = EfiEventEmptyFunction;\r
} else {\r
WorkerNotifyFunction = NotifyFunction;\r
}\r
\r
/**\r
Create, Signal, and Close the Ready to Boot event using EfiSignalEventReadyToBoot().\r
- \r
+\r
This function abstracts the signaling of the Ready to Boot Event. The Framework moved\r
from a proprietary to UEFI 2.0 based mechanism. This library abstracts the caller\r
from how this event is created to prevent to code form having to change with the\r
\r
\r
/**\r
- Check to see if the Firmware Volume (FV) Media Device Path is valid \r
- \r
- The Framework FwVol Device Path changed to conform to the UEFI 2.0 specification. \r
+ Check to see if the Firmware Volume (FV) Media Device Path is valid\r
+\r
+ The Framework FwVol Device Path changed to conform to the UEFI 2.0 specification.\r
This library function abstracts validating a device path node.\r
- Check the MEDIA_FW_VOL_FILEPATH_DEVICE_PATH data structure to see if it's valid. \r
- If it is valid, then return the GUID file name from the device path node. Otherwise, \r
- return NULL. This device path changed in the DXE CIS version 0.92 in a non back ward \r
- compatible way to not conflict with the UEFI 2.0 specification. This function abstracts \r
+ Check the MEDIA_FW_VOL_FILEPATH_DEVICE_PATH data structure to see if it's valid.\r
+ If it is valid, then return the GUID file name from the device path node. Otherwise,\r
+ return NULL. This device path changed in the DXE CIS version 0.92 in a non back ward\r
+ compatible way to not conflict with the UEFI 2.0 specification. This function abstracts\r
the differences from the caller.\r
If FvDevicePathNode is NULL, then ASSERT().\r
\r
\r
/**\r
Initialize a Firmware Volume (FV) Media Device Path node.\r
- \r
- The Framework FwVol Device Path changed to conform to the UEFI 2.0 specification. \r
- This library function abstracts initializing a device path node. \r
- Initialize the MEDIA_FW_VOL_FILEPATH_DEVICE_PATH data structure. This device \r
- path changed in the DXE CIS version 0.92 in a non back ward compatible way to \r
- not conflict with the UEFI 2.0 specification. This function abstracts the \r
+\r
+ The Framework FwVol Device Path changed to conform to the UEFI 2.0 specification.\r
+ This library function abstracts initializing a device path node.\r
+ Initialize the MEDIA_FW_VOL_FILEPATH_DEVICE_PATH data structure. This device\r
+ path changed in the DXE CIS version 0.92 in a non back ward compatible way to\r
+ not conflict with the UEFI 2.0 specification. This function abstracts the\r
differences from the caller.\r
If FvDevicePathNode is NULL, then ASSERT().\r
If NameGuid is NULL, then ASSERT().\r
- \r
+\r
@param FvDevicePathNode The pointer to a FV device path node to initialize\r
@param NameGuid FV file name to use in FvDevicePathNode\r
\r
projects / mirror_edk2.git / blobdiff