USB "Vendor class" to support future devices

NTDEV
1

I have a client where I’m fixing up their driver. They would like it if it were possible such that any new devices (same VID, different PID) will get loaded. I’m trying to figure out how to have a compatible ID of sorts. Is there a way to do this without going through the USB-IF?

2

xxxxx@gmail.com wrote:

I have a client where I’m fixing up their driver. They would like it if it were possible such that any new devices (same VID, different PID) will get loaded. I’m trying to figure out how to have a compatible ID of sorts. Is there a way to do this without going through the USB-IF?

Well, it depends on how comfortable you are. You could choose a
bDeviceSubClass and bDevice Protocol, and decide you’ll use that for all
of your future devices. Now, you can write an INF that matches
USB\Class_FF&SubClass_39&Prot_03.

I don’t think you could ever pass such a driver past WHQL, since there’s
nothing to prevent some other manufacturer from choosing the same code.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Tim,

Thanks for your response. I want a clean solution that won’t cause issues in the future. My guess is that it isn’t possible based on my experience and research. But I had to at least ask the experts just in case I have missed something.

4

Why don’t you just pick some PIDs now, and put them in the INF. When they come up with the new hardware, use those PIDs already chosen. I’ve seen INFs with MANY unique PnP IDs, and can’t imagine WHQL testing was done for each and every one.

Jan

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Friday, May 30, 2014 2:11 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] USB “Vendor class” to support future devices

I have a client where I’m fixing up their driver. They would like it if it were possible such that any new devices (same VID, different PID) will get loaded. I’m trying to figure out how to have a compatible ID of sorts. Is there a way to do this without going through the USB-IF?

5

Jan,

I should have mentioned that was discussed. I can’t even get that from the client, and I didn’t want to have 65,536 entries in the .inf file!

6

Is it a hard requirement that “new device” == new PID?

7

Chris,

I believe the answer is yes. I think that my gut feeling is correct in that my client will have to modify the .inf file for each new device with the PID (and a friendly name) and re-certify.

8

For “custom” libusb-handled devices and certain other classes, you can
get a free ID:

https://github.com/obdev/v-usb/blob/master/usbdrv/USB-IDs-for-free.txt

– pa