![Intel Extensible Firmware Interface Specification Download Page 91](http://html1.mh-extra.com/html/intel/extensible-firmware-interface/extensible-firmware-interface_specification_2073117091.webp)
Services
Version 1.02
12/12/00
73
3.4.4 EFI_IMAGE_ENTRY_POINT
Summary
This is the declaration of an EFI image entry point. This can be the entry point to an EFI
application, an EFI boot service driver, or an EFI runtime driver.
Prototype
typedef
EFI_STATUS
(EFIAPI *EFI_IMAGE_ENTRY_POINT) (
IN EFI_HANDLE
ImageHandle,
IN EFI_SYSTEM_TABLE
*SystemTable
);
Parameters
ImageHandle
Handle that identifies the loaded image. Type
EFI_HANDLE
is defined
in Section 3.3.1.
SystemTable
System Table for this image. Type
EFI_SYSTEM_TABLE
is defined in
Chapter 4.
Description
An image’s entry point is of type
EFI_IMAGE_ENTRY_POINT
. After firmware loads an image
into memory, control is passed to the image’s entry point. The entry point is responsible for
initializing the image. The image’s
ImageHandle
is passed to the image. The
ImageHandle
provides the image with all the binding and data information it needs. This information is available
through protocol interfaces. However, to access the protocol interfaces on
ImageHandle
requires access to boot services functions. Therefore,
LoadImage()
passes to the
EFI_IMAGE_ENTRY_POINT
a
SystemTable
that is inherited from the current scope of
LoadImage()
.
All image handles support the
LOADED_IMAGE
protocol. This protocol can be used to obtain
information about the loaded image’s state — for example, the device from which the image was
loaded and the image’s load options. In addition, the
ImageHandle
may support other protocols
provided by the parent image.
If the image supports dynamic unloading, it must supply an unload function in the
LOADED_IMAGE
structure before returning control from its entry point.
In general, an image returns control from its initialization entry point by calling
Exit()
or by
returning control from its entry point. If the image returns control from its entry point, the
firmware passes control to
Exit()
using the return code as the
ExitStatus
parameter to
Exit()
.
See
Exit()
for entry point exit conditions (Section 3.4.5).
Summary of Contents for Extensible Firmware Interface
Page 1: ...Extensible Firmware Interface Specification Version 1 02 December 12 2000...
Page 4: ...Extensible Firmware Interface Specification iv 12 12 00 Version 1 02...
Page 42: ...Extensible Firmware Interface Specification 24 12 01 00 Version 1 02...
Page 190: ...Extensible Firmware Interface Specification 172 12 12 00 Version 1 02...
Page 200: ...Extensible Firmware Interface Specification 182 12 12 00 Version 1 02...
Page 226: ...Extensible Firmware Interface Specification 208 12 12 00 Version 1 02...
Page 230: ...Extensible Firmware Interface Specification 212 12 12 00 Version 1 02...
Page 252: ...Extensible Firmware Interface Specification 234 12 12 00 Version 1 02...
Page 294: ...Extensible Firmware Interface Specification 276 12 12 00 Version 1 02...
Page 348: ...Extensible Firmware Interface Specification 330 12 01 00 Version 1 01...
Page 350: ...Extensible Firmware Interface Specification 332 12 12 00 Version 1 02...
Page 354: ...Extensible Firmware Interface Specification 336 12 12 00 Version 1 02...
Page 362: ...Extensible Firmware Interface Specification 344 12 12 00 Version 1 02...
Page 486: ...Extensible Firmware Interface Specification 468 12 12 00 Version 1 02...
Page 494: ...Extensible Firmware Interface Specification 476 12 12 00 Version 1 02...