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
10 UEFI Service Binding Protocol
11 UEFI Driver and Controller Names
12 UEFI Driver Configuration
13 UEFI Driver Diagnostics
14 Driver Health Protocol
14.1 Driver Health Protocol Implementation
14.2 GetHealthStatus() Implementations
14.3 Repair() Implementation
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
14 Driver Health Protocol
The Driver Health Protocol is a feature potentially required by UEFI Drivers following the UEFI Driver Model. If a UEFI Driver needs to report health status to the platform, provide warning or error messages to the user, perform length repair operations, or request that the user make hardware or software configuration changes, the Driver Health Protocol must be produced. This protocol is required only for devices potentially in a bad state and recoverable through either a repair operation or configuration change. The Driver Health Protocol should not be implemented if a device can never be in a bad state or a device can be in a bad state for which no remediation is possible.
The UEFI Boot Manager uses the services of the Driver Health Protocol, if present, to determine the health status of a device and display that status information on a UEFI console. The UEFI Boot Manager may also choose to perform actions to transition devices from a bad state to a usable state. See the EFI Driver Health Protocol section of the UEFI Specification for more details on how a UEFI Boot manager interacts with the Driver Health Protocol.
This chapter focuses on how to implement the Driver Health Protocol for a UEFI Driver managing a specific set of devices.
Previous
13.3 Testing Driver Diagnostics Protocols
Next
14.1 Driver Health Protocol Implementation
Last modified 1yr ago
Copy link