Intel Extensible Firmware Interface Specification page 229

If is
BootPolicy FALSE
exists,
EFI_NOT_FOUND
to perform a network boot through the PXE Base Code protocol,
If is
BootPolicy TRUE
boot selection. In this case,
Normally the firmware would implement the policy on how to handle an inexact boot file path;
however, since in this case the firmware cannot interpret the file path, the
is responsible for implementing the policy. For example, in the case of a network boot through the
PXE Base Code protocol,
interprets this as wanting to boot from the first valid loader. The following is list of events that
will implement for a PXE boot:
LoadFile()
•
Perform DHCP.
•
Optionally prompt the user with a menu of boot selections.
•
Discover the boot server and the boot file.
•
Download the boot file into
Status Codes Returned
EFI_SUCCESS
EFI_UNSUPPORTED
EFI_INVALID_PARAMETER
EFI_NO_SUCH_MEDIA
EFI_DEVICE_ERROR
EFI_NO_RESPONSE
EFI_NOT_FOUND
EFI_ABORTED
Version 1.02
the must match an exact file to be loaded. If no such file
FilePath
is returned. If
BootPolicy
the firmware's boot manager is attempting to load an EFI image that is a
contains the file path value in the boot selection option.
FilePath
merely points to the root of the device, and the firmware
FilePath
and update
Buffer
The file was loaded.
The device does not support the provided
FilePath is not a valid device path, or
No medium was present to load the file.
The file was not loaded due to a device error.
The remote system did not respond.
The file was not found.
The file load process was manually cancelled.
12/12/00
is FALSE, and an attempt is being made
EFI_UNSUPPORTED
LoadFile()
with the size of the boot file.
BufferSize
BootPolicy
BufferSize
Load File Protocol
is returned.
function
.
is .
NULL
211