Most drivers complete some I/O requests but pass other requests down the device stack. Drivers can also create I/O requests. Whether your driver creates new requests or simply passes down requests that it receives from the framework, the destination for that request is an I/O target.
This chapter starts with basic information about I/O targets. It then describes how a driver can create and format an I/O request and send the request to an I/O target.
For this chapter, you need … | From … |
---|---|
| |
Samples | |
Echo_driver | %wdk%\Src\Umdf\Usb\Echo_driver |
Filter | %wdk%\Src\Umdf\Usb\Filter |
Fx2_Driver | %wdk%\Src\Umdf\Usb\Fx2_driver |
Kbfiltr | %wdk%\Src\Kmdf\Kbfiltr\Sys |
Ndisedge | %wdk%\Src\Kmdf\Ndisedge\60 |
Osrusbfx2 | %wdk%\Src\Kmdf\Osrusbfx2\Sys\Final |
Toastmon | %wdk%\Src\Kmdf\Toaster\Toastmon |
Usbsamp | %wdk%\Src\Kmdf\Usbsamp |
WDK documentation | |
ACCESS_MASK | http://go.microsoft.com/fwlink/?LinkId=80616 |
Handling I/O Requests in Framework-based Drivers | http://go.microsoft.com/fwlink/?LinkId=80613 |
Object Names | http://go.microsoft.com/fwlink/?LinkId=80615 |
Specifying WDF Directives | http://go.microsoft.com/fwlink/?LinkId=82953 |
WINUSB_SETUP_PACKET | http://go.microsoft.com/fwlink/?LinkId=83355 |