USB Compsite Device Driver loading and PnP events

I have a question on the USB composite device. In DDK, it is said After the
USB hub driver generates a PnP event for a Composite device with a set of
compatible IDs that include USB\COMPOSITE, Windows searches the INF files in
the inf subdirectory of the Windows installation (and, possibly, a
vendor-provided floppy disk) for a match. If the device ID is matched,
Windows loads the single driver that is indicated by the installation script
and the generic parent driver does not come into play. If no device ID match
is found, Windows uses a compatible ID, for which it loads the USB generic
parent driver.

I just want to know If the device ID is matched, Windows loads the single
driver that is indicated by the installation scripts, then who will be
responsible to generates PnP events for the multiple interfaces in the
composite device?

Doron
Thu Mar 08 00:48:02 CST 2007

the driver that is loaded by the INF (e.g. not the generic parent driver).
typicaly this type of driver will not expose the multiple interfaces in the
composite device as separate functions, rather it will consume all of the
interfaces as one function. for instance, a bluetooth radio is 2 interfaces
(one for isoch, the other for bulk/int data). the bth radio stack consumes
both interfaces directly and does not enumerate them as separate functions.

are you encountering a problem that you are trying to solve or just trying
to figure out how things work generically?

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Kevin" <Kevin@discussions.microsoft.com> wrote in message
news:6676459F-C0DC-40FA-B1B7-2D6501B4BE21@microsoft.com...
>I have a question on the USB composite device. In DDK, it is said After the
> USB hub driver generates a PnP event for a Composite device with a set of
> compatible IDs that include USB\COMPOSITE, Windows searches the INF files
> in
> the inf subdirectory of the Windows installation (and, possibly, a
> vendor-provided floppy disk) for a match. If the device ID is matched,
> Windows loads the single driver that is indicated by the installation
> script
> and the generic parent driver does not come into play. If no device ID
> match
> is found, Windows uses a compatible ID, for which it loads the USB generic
> parent driver.
>
> I just want to know If the device ID is matched, Windows loads the single
> driver that is indicated by the installation scripts, then who will be
> responsible to generates PnP events for the multiple interfaces in the
> composite device?