4 ms·
They have: "There are a number of ideas to get around VTM Group that include squatting on USB VID 0xF055"
by ZeroGravitas 13y ago
They have:
"There are a number of ideas to get around VTM Group that include squatting on USB VID 0xF055"
- StavrosK 13y agoHah, nice VID, easy to remember.
- qwerty_asdf 13y agoDoes anybody own these? 0xDEAD 0xBEEF 0x1337 0xFACE 0xF00D 0xABCD ...and so on? Maybe, if they're reserved as unassignable (due to being an inappropriate value for professional, business puposes), then perhaps it's open season on those.
- nraynaud 13y agoI think 0xF055 has circulated too much now (slashdot, hack a day, maker: etc.) So if we there should be squatting it better be on 0xF055. Let's just destroy the strict minimum to achieve our goal (having a unique VID+PID for our proprietary drivers to find the corresponding gadget on the bus).
- rtkwe 13y agoLooks like no: http://www.linux-usb.org/usb.ids http://www.linux-usb.org/usb.ids Though I'm not sure how accurate and complete this list is. Edit the official list is here but they list their VIDs in dec.
- Amadou 13y agoAn alternative would be to find one that has been assigned to a now defunct company. Then you'd only have to worry about historical devices and if you are lucky you could come up with a list of those PIDs and exclude them.
- missing_cipher 13y agoFor those who missed it, 0xF055 can be read as "FOSS": http://en.wikipedia.org/wiki/Free_and_open-source_software http://en.wikipedia.org/wiki/Free_and_open-source_software