News for hackers. Stuff that matters.
Re:USB Implementers Forum Says No to Open Source by nraynaud on Tuesday October 22, 2013 @09:49AM (#6591838)
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.

Re:USB Implementers Forum Says No to Open Source by nitrogen on Tuesday October 22, 2013 @11:15AM (#6592436)
I 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".
Re:USB Implementers Forum Says No to Open Source by pyre on Tuesday October 22, 2013 @09:30PM (#6596153)
Try searching this:

  development usb "vid" -video
First hit is someone asking about VID/PID in a motherboard forum.
Re:USB Implementers Forum Says No to Open Source by dylz on Wednesday October 23, 2013 @03:07AM (#6597346)
Search Tools > Verbatim
Re:USB Implementers Forum Says No to Open Source by nicksdjohnson on Tuesday October 22, 2013 @10:09AM (#6591959)
VIDs and PIDs are 16 bits, not 8.
Re:USB Implementers Forum Says No to Open Source by nraynaud on Tuesday October 22, 2013 @10:12AM (#6591981)
oops, 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.
Re:USB Implementers Forum Says No to Open Source by dkersten on Tuesday October 22, 2013 @05:02PM (#6594956)
When 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.