Extensible Firmware Interface Specification
Description
The
LoadImage()
The image is loaded in one of two ways. If
memory-to-memory load in which
indicates the image's size in bytes. In this case, the caller has copied the image into
SourceSize
and can free the buffer once loading is complete.
SourceBuffer
If
SourceBuffer
SIMPLE_FILE_SYSTEM
access the file referred to by FilePath. In this case, the
LOAD_FILE.LoadFile()
when the
FilePath
Load File Protocol in Chapter 11.
Regardless of the type of load (memory-to-memory or file copy), the function relocates the code in
the image while loading it.
Once the image is loaded, firmware creates and returns an
and supports the
LOADED_IMAGE
or add additional protocol support to the handle before passing control to the newly loaded image
by calling StartImage(). Also, once the image is loaded, the caller either starts it by calling
or unloads it by calling Unload().
StartImage()
Status Codes Returned
EFI_SUCCESS
EFI_NOT_FOUND
EFI_INVALID_PARAMETER
EFI_UNSUPPORTED
EFI_OUT_OF_RESOURCES
EFI_LOAD_ERROR
EFI_DEVICE_ERROR
70
function loads an EFI image into memory and returns a handle to the image.
SourceBuffer
SourceBuffer
is NULL, the function is a file copy operation that uses the
protocol and then the
function and is used to load the default image responsible for booting
only indicates the device. For more information see the discussion of the
protocol. The caller may fill in the image's "load options" data,
Image was loaded into memory correctly.
The
FilePath
One of the parameters has an invalid value.
The image type is not supported, or the device path can not be
parsed to locate the proper protocol for loading the the file.
Image was not loaded due to insufficient resources.
Image was not loaded because the image format was corrupt or not
understood.
Image was not loaded because the device returned a read error.
12/12/00
is not NULL, the function is a
points to the image to be loaded and
protocol on the
LOAD_FILE
BootPolicy
EFI_HANDLE
was not found.
to
DeviceHandle
flag is passed to the
that identifies the image
Version 1.02
Need help?
Do you have a question about the Extensible Firmware Interface and is the answer not in the manual?