EDK II UEFI Driver Writer's Guide
Search…
EDK II UEFI Driver Writer's Guide
Introduction
Tables
Figures
Examples
Acknowledgements
1 Introduction
2 UEFI Driver Implementation Checklist
3 Foundation
4 General Driver Design Guidelines
5 UEFI Services
6 UEFI Driver Categories
7 Driver Entry Point
8 Private Context Data Structures
9 Driver Binding Protocol
9.1 Driver Binding Protocol Implementations
9.2 Driver Binding Protocol Template
9.3 Testing Driver Binding Protocol
10 UEFI Service Binding Protocol
11 UEFI Driver and Controller Names
12 UEFI Driver Configuration
13 UEFI Driver Diagnostics
14 Driver Health Protocol
15 Driver Family Override Protocol
16 Driver Supported EFI Version Protocol
17 Bus-Specific Driver Override Protocol
18 PCI Driver Design Guidelines
19 USB Driver Design Guidelines
20 SCSI Driver Design Guidelines
21 ATA Driver Design Guidelines
22 Text Console Driver Design Guidelines
23 Graphics Driver Design Guidelines
24 Mass Storage Driver Design Guidelines
25 Network Driver Design Guidelines
26 User Credential Driver Design Guidelines
27 Load File Driver Design Guidelines
28 IPF Platform Porting Considerations
29 EFI Byte Code Porting Considerations
30 Building UEFI Drivers
31 Testing and Debugging UEFI Drivers
32 Distributing UEFI Drivers
Appendix A EDK II File Templates
Appendix B EDK II Sample Drivers
Appendix C Glossary
Powered By GitBook
9 Driver Binding Protocol
The Driver Binding Protocol provides services to do the following:
  • Connect a driver to a controller.
  • Disconnect a driver from a controller.
UEFI drivers following the UEFI driver model are required to implement the Driver Binding Protocol. This requirement includes the following drivers:
  • Device drivers
  • Bus drivers
  • Hybrid drivers
Root bridge driver, service drivers, and initializing drivers do not produce this protocol.
The Driver Binding Protocol is the most important protocol that a driver produces. It is the one protocol used by the UEFI boot services ConnectController() and DisconnectController(). These UEFI boot services are used by the UEFI boot manager to connect the console and boot devices required to boot an operating system. The implementation of the Driver Binding Protocol varies depending upon the driver's category. Chapter 6 of this guide describes the various driver categories.
Previous
8.5 Retrieving private context data structures
Next
9.1 Driver Binding Protocol Implementations
Last modified 1yr ago
Copy link