Intel Extensible Firmware Interface Specification page 264

Extensible Firmware Interface Specification
Description
The basic mechanisms and flow for remote booting in EFI are identical to the remote boot
functionality described in detail in the PXE Specification. However, the actual execution
environment, linkage, and calling conventions are replaced and enhanced for the EFI environment.
The DHCP Option for the Client System Architecture is used to inform the DHCP server if the
client is an IA-32 or Itanium-based EFI environment. The server may use this information to
provide default images if it does not have a specific boot profile for the client.
A handle that supports
protocol. The
LOAD_FILE
from devices that do not support file system type accesses. Specifically, the firmware's boot
manager invokes
LoadFile()
the device. The firmware then loads and transfers control to the downloaded PXE boot image.
Once the remote image is successfully loaded, it may utilize the
interfaces, or even the
246
EFI_PXE_BASE_CODE
protocol function
LoadFile()
with
BootPolicy
EFI_SIMPLE_NETWORK
12/12/00
protocol is required to support the
is used by the firmware to load files
being when attempting to boot from
TRUE
EFI_PXE_BASE_CODE
interfaces, to continue the remote process.
LOAD_FILE
Version 1.02