EFI资料翻译EFI概述2

UEFI
uefi关键内容
1. Objects-管理系统&＃xff08;包括I/O设备&＃xff0c;memory&＃xff0c;events&＃xff09;的状态。
2. The UEFI System Table-data structure with data in-formation tables to interface with the systems
3. .Handle database and protocols- callable interfaces that are registered
4. UEFI Image-the executable content format.
5. Events-the software can be signed in response to some other activity.(软件可以被信号通知以做出一些反应)
6. Device paths-a data structure that describes the hardware location of an entity

什么是GUID?
1. GUID—guaranteed&＃xff08;Globally&＃xff09; Unique Identifiers&＃xff08;设定的唯一标识符&＃xff09;&＃xff0c;总共128个bit。
2. Used to identify protocols-用于去识别协议。
3. Regulate extension mechanism-控制扩展机制。
–Documented in the spec
–Added through drivers

Handles:
.所有的协议都有一个Handles和其联系在一起的。
. Every device and executable image in EFI has a handle protocol in the handle database.


What is the UEFI System Table?
.Firmware implementation information
-外围设备只能读取Table数据。
-Spec version。
-UEFI protocols的接口。
-其他标准的接口。

Device path protocol&＃xff1a;
-一个描述一个设备在platform中位置的数据结构。
-ALL boot device&＃xff0c;logical devices and images 都必须被一个device path所描述。
-device path的6types&＃xff1a;
.Hardware
.Acpi-uid/hid of device of in AMI
.Message-例如&＃xff1a;LAN, Fiber Channel&＃xff0c; ATAPI, SCSI, USB.
   .Media-HD, Floppy&＃xff0c;CD-ROM.
.EDD 3.0 boot device—see EDD 3.0 SPEC INT13 48.
.End of hardware-marks end of device path。
What are UEFI Boot services?
.Events and notifications
-polled(轮询) devices&＃xff0c;no interrupts
.watchdog timer
- Elegant recovery
.Memory allocation(内存分配)
.Handle location ––for finding protocols
.Image loading
-Drivers, application, OS loader

UEFI Runtime Services:
.Services available at both boot time and runtime.
.Timer, wakeup alarm
-Allow system to wake up or power on at a set time.
.Variables
-boot manager handshake.
.System reset.

UEFI Driver Design
. Modular chunks(大块的) of code run in pre-boot。
-manage devices or services.
-..they are NOT OS-present drivers!.(他们不是使OS出现的驱动)。
.Drivers export(输出) protocol(协议) interfaces
-protocol&＃61;instance(实例) data &＃43; access methods.
- Like C&＃43;&＃43; classes but more code space efficient&＃xff08;效率&＃xff09;。
- Identified by GUID to avoid collisions&＃xff08;冲突&＃xff09;。
- Version numbers and signatures provide means to manage driver management policy
.Drivers may consume(占用) protocol interfaces。
-self-describing the dependencies.
-E.g. memory initialization may depend on SMBUS service

UEFI Driver Model:
.Used for devices on industry standard bus.
-“boot devices”
.Structured model of device/bus hierarchy(层次).
-device drivers and bus drivers。
-Device drivers are topology(拓扑结构) agnostic.
.Benefits(好处)
-simpler device drivers
   -把复杂性都移进入BUS drivers 和core services
   -Smaller drivers footprint&＃xff08;占用&＃xff1f;&＃xff09;。
-通过platform来确定性的选择驱动
   -which driver controls which device。
-Describes 复杂的bus hierarchies&＃xff08;层次&＃xff09;。
-Embedded, Desktop, Workstation, Server
-Extensible to future bus types

BUS DRIVER:
. Consumes&＃xff08;消耗&＃xff09; Parent Bus I/O Abstraction(s)。
.initializes bus controller(初始化bus控制器).
.Allocates Resources for child controllers.-分配资源给子控制器
.Creates Handles for child controllers.
. Loads drivers from Option ROMs if present-从option ROM载入驱动。

DEVICE DRIVER:

.Consumes&＃xff08;消耗&＃xff09; bus i/o abstraction&＃xff08;s&＃xff09;。

.initializes device controller

.produces device abstraction(s)

-Block i/o protocol

-simple text output protocol.

-simple Network protocol.

.Does not create any child handles.

.can still be a “parent” controller.

DEIVER Initialization:

.EFI Driver handoff state.

.Not allowed to touch hardware resources.

Installs driver binding on driver image handle.