【正文】
ver footprint ? Deterministic driver selection by the platform Which driver controls which device ? Describes plex bus hierarchies Embedded, Desktop, Workstation, Server ? Extensible to future bus types 繼續(xù) 返回 Driver model a sample desktop system 繼續(xù) 返回 Driver model Server System 繼續(xù) 返回 Driver Initialization Step 1: the boot service LoadImage(). 繼續(xù) 返回 Driver Initialization Step 2: the boot service StartImage(). 繼續(xù) 返回 Host Bus Controllers This initial collection of controllers is known as the Host Bus Controllers. Host Bus Controllers a platform with n processors (CPUs), and a set of core chipset ponents that produce m host bridges. 繼續(xù) 返回 Host Bus Controllers Each host bridge(HB) is represented in UEFI as a device handle that contains a Device Path Protocol instance, and a protocol instance that abstracts the I/O operations that the host bus can perform. PCI Root Bridge Device Handle 繼續(xù) 返回 Device Drivers Each host bridge(HB) is represented in UEFI as a device handle that contains a Device Path Protocol instance, and a protocol instance that abstracts the I/O operations that the host bus can perform. PCI Root Bridge Device Handle 繼續(xù) 返回 Bus Drivers Bus drivers and device drivers are virtually identical from the UEFI Driver Model’s point of view. The only difference is that a bus driver creates new device handles for the child controllers that the bus driver discovers on its bus. Child Device Handle with a Bus Specific Override 繼續(xù) 返回 Driver Design Steps ? Driver or Application ? Determine the driver’s type ? Identify I/O protocols to be consumed ? Identify I/O protocols to produce ? Implement UEFI driver model protocols ? Implement specific protocols All Drivers Service Drivers Initializing Drivers UEFI Driver Model Device Drivers Bus Drivers Hybrid Drivers Root Bridge Drivers 繼續(xù) 返回 Agenda ? UEFI Forum ? UEFI Technical Concept – Boot support – Key Elements – Boot Service – Runtime Service – UEFI Driver Model – EFI Byte Code ? Summary 繼續(xù) 返回 EFI Byte Code Legacy 16/32 bit EFI Byte Code MEMORY IA32 (BIOS) IA32 (EFI) Itanium ? Single image supports multiple platforms ? Code is interpreted on Intel Itanium174。 Architecture and IA32 systems ? IHVs develop only once 繼續(xù) 返回 Agenda ? UEFI Forum ? UEFI Technical Concept – Boot support – Key Elements – Boot Service – Runtime Service – UEFI Driver Model – EFI Byte Code ? Summary 繼續(xù) 返回 Summary ?UEFI settle interface firmly on the Industry’s Roadmap ?UEFI breaks through fundamental BIOS barriers ?UEFI solves legacy Option ROM problems ?UEFI offers flexible solution to meet existing and future need