 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
After the USBD module loads a USB device driver for a peripheral, it calls the driver's USBDeviceAttachfunction. In this function, the driver performs the following operations:
- Determines whether it can control the peripheral. If the driver can control the peripheral, it returns TRUE to accept control. Otherwise, the driver returns FALSE to decline control. In the latter case, the USBD module continues to search for other drivers to control the peripheral.
- Loads additional USB device drivers for other interfaces that may be present on the peripheral by calling the LoadGenericInterfaceDriverfunction. If a USB device driver accepts control of a peripheral, the USBD module stops searching for drivers to control the peripheral. The driver that accepts control must then load any other USB device drivers for other interfaces present on the peripheral.
- Registers a callback function that is called when the
peripheral is disconnected from the bus. USB device drivers use the
RegisterNotificationRoutinefunction to register callback
functions.
Last updated on Tuesday, July 13, 2004
© 2004 Microsoft Corporation. All rights reserved.