I have searched high and low in the DDK and MSDN doucmentation and can’t find information on speficying an interface when specifying a USB PID & VID in a .inf file.
Can some enlightened soul pleasde point me to the documentation.
I have a USB device with two interfaces and I want my dirver to handle the second one only.
Thanks
Larry
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
Larry,
This is in even the earlier Windows XP DDK docs for sure (search on
“multiple-interface”).
It’s like this:
USB\VID_XXXX&PID_YYYY&MI_ZZ
XXXX = VID
YYYY = PID
ZZ = zero-based interface number, two digits with leading zero. ‘PIC 99’ if
you will…
-Tim
Timothy A. Johns — xxxxx@driverdev.com
Driver Development Corporation — 800.841.0092
Bring Up Your Hardware — Fast. www.driverdev.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Harmon, Larry CT
Sent: Wednesday, August 08, 2001 8:50 AM
To: NT Developers Interest List
Subject: [ntdev] USB Hardware ID interface qualifierI have searched high and low in the DDK and MSDN doucmentation
and can’t find information on speficying an interface when
specifying a USB PID & VID in a .inf file.Can some enlightened soul pleasde point me to the documentation.
I have a USB device with two interfaces and I want my dirver to
handle the second one only.Thanks
Larry
You are currently subscribed to ntdev as: xxxxx@driverdev.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
Thanks Tim,
I have the Win2k DDK installed and couldn’t find this info.
Larry
-----Original Message-----
From: Timothy A. Johns [mailto:xxxxx@driverdev.com]
Sent: Wednesday, August 08, 2001 2:05 PM
To: NT Developers Interest List
Subject: [ntdev] RE: USB Hardware ID interface qualifier
Larry,
This is in even the earlier Windows XP DDK docs for sure (search on
“multiple-interface”).
It’s like this:
USB\VID_XXXX&PID_YYYY&MI_ZZ
XXXX = VID
YYYY = PID
ZZ = zero-based interface number, two digits with leading zero. ‘PIC 99’ if
you will…
-Tim
Timothy A. Johns — xxxxx@driverdev.com
Driver Development Corporation — 800.841.0092
Bring Up Your Hardware — Fast. www.driverdev.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Harmon, Larry CT
Sent: Wednesday, August 08, 2001 8:50 AM
To: NT Developers Interest List
Subject: [ntdev] USB Hardware ID interface qualifierI have searched high and low in the DDK and MSDN doucmentation
and can’t find information on speficying an interface when
specifying a USB PID & VID in a .inf file.Can some enlightened soul pleasde point me to the documentation.
I have a USB device with two interfaces and I want my dirver to
handle the second one only.Thanks
Larry
You are currently subscribed to ntdev as: xxxxx@driverdev.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@diebold.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
Larry,
The Win2K DDK docs are much better than the NT 4.0 docs, and the XP docs are
substantially better than those. I’d recommend installing the latest XP DDK
if just for the docs. With regard to multiple interface (composite) USB
devices, the XP DDK docs not only give the format of the hardware ID, but
also explains the mechanism for selecting which INF to use, etc. Good
stuff.
-Tim
Timothy A. Johns — xxxxx@driverdev.com
Driver Development Corporation — 800.841.0092
Bring Up Your Hardware — Fast. www.driverdev.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Harmon, Larry CT
Sent: Wednesday, August 08, 2001 12:33 PM
To: NT Developers Interest List
Subject: [ntdev] RE: USB Hardware ID interface qualifierThanks Tim,
I have the Win2k DDK installed and couldn’t find this info.
Larry
-----Original Message-----
From: Timothy A. Johns [mailto:xxxxx@driverdev.com]
Sent: Wednesday, August 08, 2001 2:05 PM
To: NT Developers Interest List
Subject: [ntdev] RE: USB Hardware ID interface qualifierLarry,
This is in even the earlier Windows XP DDK docs for sure (search on
“multiple-interface”).It’s like this:
USB\VID_XXXX&PID_YYYY&MI_ZZ
XXXX = VID
YYYY = PID
ZZ = zero-based interface number, two digits with leading zero.
‘PIC 99’ if
you will…-Tim
Timothy A. Johns — xxxxx@driverdev.com
Driver Development Corporation — 800.841.0092
Bring Up Your Hardware — Fast. www.driverdev.com> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Harmon, Larry CT
> Sent: Wednesday, August 08, 2001 8:50 AM
> To: NT Developers Interest List
> Subject: [ntdev] USB Hardware ID interface qualifier
>
>
> I have searched high and low in the DDK and MSDN doucmentation
> and can’t find information on speficying an interface when
> specifying a USB PID & VID in a .inf file.
>
> Can some enlightened soul pleasde point me to the documentation.
>
> I have a USB device with two interfaces and I want my dirver to
> handle the second one only.
>
> Thanks
>
> Larry
>
> —
> You are currently subscribed to ntdev as: xxxxx@driverdev.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
You are currently subscribed to ntdev as: xxxxx@diebold.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@driverdev.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
Tim,
Thanks for the info. I will install it and look at the USB info.
I have been able to get multiple interfaces working. And I discovered a couple things along the way.
For instance, when I get the configuration descriptor, it says there is only 1 interface! But my device has two interfaces and both caused a AddDevice call to be made. It seems that using the &MI_xx qualifier in the .inf file causes microsoft to hide the other interfaces. Calls to USBD_ParseConfigurationDescriptorEx also do not return information about other interfaces. This means the example given in the DDK documentation for calling USBD_ParseConfigurationDescriptorEx doesn’t work. The call must be modified to pass a -1 for the interface number, then it will return a good interface descriptor.
Just thought I would pass this information along.
Larry
-----Original Message-----
From: Timothy A. Johns [mailto:xxxxx@driverdev.com]
Sent: Thursday, August 09, 2001 10:54 AM
To: NT Developers Interest List
Subject: [ntdev] RE: USB Hardware ID interface qualifier
Larry,
The Win2K DDK docs are much better than the NT 4.0 docs, and the XP docs are
substantially better than those. I’d recommend installing the latest XP DDK
if just for the docs. With regard to multiple interface (composite) USB
devices, the XP DDK docs not only give the format of the hardware ID, but
also explains the mechanism for selecting which INF to use, etc. Good
stuff.
-Tim
Timothy A. Johns — xxxxx@driverdev.com
Driver Development Corporation — 800.841.0092
Bring Up Your Hardware — Fast. www.driverdev.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Harmon, Larry CT
Sent: Wednesday, August 08, 2001 12:33 PM
To: NT Developers Interest List
Subject: [ntdev] RE: USB Hardware ID interface qualifierThanks Tim,
I have the Win2k DDK installed and couldn’t find this info.
Larry
-----Original Message-----
From: Timothy A. Johns [mailto:xxxxx@driverdev.com]
Sent: Wednesday, August 08, 2001 2:05 PM
To: NT Developers Interest List
Subject: [ntdev] RE: USB Hardware ID interface qualifierLarry,
This is in even the earlier Windows XP DDK docs for sure (search on
“multiple-interface”).It’s like this:
USB\VID_XXXX&PID_YYYY&MI_ZZ
XXXX = VID
YYYY = PID
ZZ = zero-based interface number, two digits with leading zero.
‘PIC 99’ if
you will…-Tim
Timothy A. Johns — xxxxx@driverdev.com
Driver Development Corporation — 800.841.0092
Bring Up Your Hardware — Fast. www.driverdev.com> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Harmon, Larry CT
> Sent: Wednesday, August 08, 2001 8:50 AM
> To: NT Developers Interest List
> Subject: [ntdev] USB Hardware ID interface qualifier
>
>
> I have searched high and low in the DDK and MSDN doucmentation
> and can’t find information on speficying an interface when
> specifying a USB PID & VID in a .inf file.
>
> Can some enlightened soul pleasde point me to the documentation.
>
> I have a USB device with two interfaces and I want my dirver to
> handle the second one only.
>
> Thanks
>
> Larry
>
> —
> You are currently subscribed to ntdev as: xxxxx@driverdev.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
You are currently subscribed to ntdev as: xxxxx@diebold.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@driverdev.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@diebold.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