Writing Windows WDMDevice Drivers Covers NT 4, Win 98, and Win 2000 Chris Cant Preface Chapter 1 Introduction The Windows Driver Model A New Frame of Mind Win32 Program Interface Conclusion Chapter 2 The Big Picture Device Driver Components Types of Device Driver Driver Choices WDM Rationale Conclusion Chapter 3 Device Driver Design Introduction Driver Design Guide Kernel Calls Processor Model Using Memory IRP Processing Conclusion Chapter 4 WDM Driver Environment System Set Up Utilities Driver Targets Driver Language and Libraries Good Code build UtilityVC++ Projects The Wdm1 Driver Code Installing Wdm1 Installation Details Managing Devices and Drivers Conclusion Chapter 5 Device Interfaces Devices Device Objects and Device Extensions Creating and Deleting Device Objects Device Names Device Interfaces Win32 Device Interface Access Conclusion Chapter 6 Testing and Debugging Test, Test, Test Driver Tests Debugging Debugging Techniques Debugging Tools DebugPrint Debugging Notes Bugcheck Codes Conclusion Chapter 7 Dispatch Routines Dispatch Routine IRPs I/O Request Packets IRP Structure Common IRP Parameters User Buffers Conclusion Chapter 8 Plug and Play and Device Stacks Design Overview Plug and Play Messages Device Enumeration Device Stacks Upper Edges Conclusion Chapter 9 Plug and Play Implementation Implementing Plug and Play Testing Wdm2 Other PnP IRPs Plug and Play Notification Advanced Plug and Play Conclusion Chapter 10 Power Management The Power Picture System Power Policies Power IRPs Device Power Policy Owner Handling Set Power IRPs Dispatch Routine Power Handling Testing Wdm2 Power Capabilities Device Capabilities Advanced Power Management Conclusion Chapter 11 Installation WDM Driver Installation Process INF Files Standard Sections INF File Section Hierarchy Cross-Platform and WDM INF Files Locating Drivers NT Style Driver Installation Installing NT Style Drivers in Windows 98 Conclusion Chapter 12 Windows Management Instrumentation Overview A WMI Driver WMI in Action Conclusion Chapter 13 Event Reporting Overview Message Files Registering as an Event Source Generating Events Testing Wdm3 Events Conclusion Chapter 14 DebugPrint Design Specification Design Implementation Test Driver Code DebugPrint Driver DebugPrint Monitor Conclusion Chapter 15 WdmIo and PHDIo Drivers Win32 Interface LPT Printer Driver Application Testing WdmIo Testing PHDIo Analyzing WdmIo and PHDIo Conclusion Chapter 16 Hardware I/O IRP Queuing Hardware Access IRP Queuing Processing Commands Cancelling Queued IRPs Cleanup IRP Handling Supplemental Device Queues Conclusion Chapter 17 Interrupt-Driven I/O Interrupt Handling WdmIo Reads and Writes Interrupt Handler Deferred Procedure Calls Timers Conclusion Chapter 18 NT Hardware NT Style Driver Construction Device Creation and Deletion Claiming Resources Translating Resources Finding Resources Conclusion Chapter 19 WDM System Drivers Writing Client Drivers Filter Drivers NT Layering Conclusion Chapter 20 The Universal Serial Bus Device Classes The Big Picture USB Low Level Structure USB Device Framework Client Design Conclusion Chapter 21 USB Driver Interface USB Client Driver Design USBDI IOCTLs Talking USB Testing UsbKbd USBDI Structure Reference USBDI URB Reference Conclusion Chapter 22 The Human Input Device Model HID Hides The HID Model HID Model Representation Conclusion Chapter 23 HID Clients HID Class Driver User Mode HID Clients Sending Output Reports Kernel Mode HID Clients Conclusion Appendix A Information Resources Newsgroups and Mail Lists Books Appendix B PC 99 Drivers The Specification IBM-Compatible PCs Changing World ACPI, OnNow, and Plug and Play PC 99 Conformance Appendix C Direct Memory Access Glossary Acronyms and Tools
Chapter 3 Device Driver Design Introduction This chapter introduces the basic concepts and structures that you will need to write drivers. Some ideas are sufficiently important and deserve to be mentioned now. All the other techniques, routines, and objects are covered in the following chapters.
Windows uses a layered design for passing requests from the end user to a driver stack and eventually to the hardware. As a trusted part of the operating system, a driver must be written well to fit into the kernel. It should use the kernel's abstract model of the processor and use memory carefully. Wherever possible, a driver should use the recommended techniques, routines, and structures.