You can find that out yourself in a debugger by using various !commands.
For example:
0: kd> !drvobj usbhub <----------- Gives you the address of the
driverobject and all the deviceobjects created by the driver.
Driver object (818c37e8) is for:
\Driver\usbhub
Driver Extension List: (id , addr)
Device Object list:
81b01cd0
0: kd> !devstack 81b01cd0 <— lists all the deviceobjects in the
stack, top down, and the name of the driver created it, device
extension, etc.
!DevObj !DrvObj !DevExt ObjectName
81b01cd0 \Driver\usbhub 81b01d88 0000004a
81b06048 \Driver\usbuhci 81b06100 USBPDO-0
!DevNode 818b8ee0 :
DeviceInst is “USB\ROOT_HUB\4&12f0dd96&0”
ServiceName is “usbhub”
Other useful commands !devobj and !devnode.
-Eliyas
-----Original Message-----
From: Mark Roddy [mailto:xxxxx@hollistech.com]
Sent: Friday, June 08, 2001 4:00 AM
To: NT Developers Interest List
Subject: [ntdev] RE: which driver creates the following PDO
-----Original Message-----
Root Hub PDO – Must be created by USBD.SYS - actually by the
adapter driver (usbuhci or usbohci,) usbd.sys is a kernel dll providing
common functionality to adapter drivers and I think usbhub as well.
Non-Root Hub PDO – created by ???
USBHUB.SYS
USB Device PDO – created by ???
USBHUB.SYS
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com