7.UEFIDevelop--同济大学BIOS和UEFI课程.ppt

UEFI与固件程序设计 Agenda EFI Driver Development EFI Application Development EFI Driver Model Supports complex bus hierarchies Follows the organization of physical/electrical architecture of the machine Driver Binding Protocol provides flexibility Function to match drivers to devices Driver version management Hot-plug and unload support Drivers not tied to FLASH Can be loaded from EFI System Partition Extensible Able to extend to future bus and device types Driver Design Steps Determine Driver Type Identify Consumed I/O Protocols Identify Produced I/O Protocols Identify EFI Driver Model Protocols Identify Additional Driver Features Identify Target Platforms x86 x64 Itanium Processor Family EFI Byte Code (EBC) What Type of Driver is Being Designed? Device Drivers Manages a Controller or Peripheral Device Start() Does Not Create Any Child Handles Start() Produces One or More I/O Protocols Installed onto the Device’s Controller Handle Bus Drivers Manages and Enumerates a Bus Controller Start() Creates One or More Child Handles Start() Produces Bus Specific I/O Protocols Installed onto the Bus’s Child Handles Hybrid Drivers Manages and Enumerates a Bus Controller Start() Creates One or More Child Handles Start() Produces Bus Specific I/O Protocols Installed onto the Bus’s Controller Handle Installed onto Bus’s Child Handles Service Drivers Does Not Manage Hardware Provides Services to other Drivers Does not support Driver Binding Protocol Typically installs protocols in driver entry point Creates One or More Service Handles Produces Service Specific Protocols Installed onto Service Handles Initializing Drivers Typically Touches Hardware Performs One Time Initialization Operations Does Not Create Any Handles Does Not Produce Any Protocols Unloaded When Finished Root Bridge Drivers Typically Manages Part of Core Chipset Directly Touches Hardware Creates One or More Root Bridge Handles Produces Root Bridge I/O Protocols Installed onto new Root a Bridge Handles What I/O