3 ms·
I think there's still a problem because that leaves still only 255 PID. Maybe we should just squat the VID, and then do a PID+(another field in the descriptor)
by nraynaud 13y ago
I think there's still a problem because that leaves still only 255 PID.
Maybe we should just squat the VID, and then do a PID+(another field in the descriptor) as the discriminator for people who need special protocols (I do).
For now I've stolen my MCU maker VID and used 255 as PID, because I couldn't even find an "experimental" PID/VID in the spec to use during development.
It's a bug and urgent problem, I'm perfectly ok to fudge the rules, but we have to agree on something that doesn't break people's drivers.
- nicksdjohnson 13y agoVIDs and PIDs are 16 bits, not 8.
- nraynaud 13y agooops, my bad! But I don't think it's enough to go random on that. We need either a registry or more bits to go random.
- nitrogen 13y agoI know I saw 0xffff or something like that being used for development in some source code, but it turns out searching for "VID" is impossible because it gets interpreted as "video".
- dkersten 13y agoWhen I was doing some development for some USB devices, I remember there was a VID/PID designated for development-only use. I can't remember what it was, however, and the company I was doing work for registered their own before the devices shipped.