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
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
20.1 SCSI Host Controller Driver
20.1.1 Single-Channel SCSI Adapters
20.1.2 Multi-Channel SCSI Adapters
20.1.3 SCSI Adapters with RAID
20.1.4 Implementing driver binding protocol
20.1.5 Implementing Extended SCSI Pass Thru Protocol
20.1.6 SCSI command set device considerations
20.1.7 Discover a SCSI channel
20.1.8 SCSI Device Path
20.2 SCSI Bus Driver
20.3 SCSI Device Driver
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
20.1.7 Discover a SCSI channel
It is recommended that the SCSI host controller driver construct a private context structure for each enumerated SCSI channel. See Chapter 8 in this guide for the advantage of using such a private context structure.
Specifically, the SCSI host controller driver should store all required information for the child SCSI channel in this data structure, this should including the signature, child handle value (optional for single channel controller), channel number, and any produced protocols. This private context structure can be accessed via the Record macro CR(), which is described in Chapter 8 of this document.
The method for determining the number of channels on a given controller is chip specific and varies by manufacturer. It is also the SCSI driver's responsibility to do the following:
  • Build the appropriate device path for the enumerated SCSI channel.
  • Install Extended SCSI Pass Thru Protocol and Device Path Protocol on the
    appropriate handle (child handle is optional for single channel).
Previous
20.1.6 SCSI command set device considerations
Next
20.1.8 SCSI Device Path
Last modified 2yr ago
Copy link