(Whoever gets "officially" issued that VID is going to whine when they notice it's already being used for hobbyist purposes anyway, which means that the technique of just picking one will guarantee uniqueness.)
(Whoever gets "officially" issued that VID is going to whine when they notice it's already being used for hobbyist purposes anyway, which means that the technique of just picking one will guarantee uniqueness.)
Edit: On second thought (after I actually read it), this bit...
Please immediately cease and desist raising funds to purchase a
unique USB VID for the purpose of transferring, reselling or
sublicensing PIDs and delete all references to the USB-IF, VIDs and
PIDs for transfer, resale or sublicense from your website and other
marketing materials.
...rubs me the wrong way on so many levels, I'm tempted to say, the hell with the forum.Which explains why we (especially) react so strongly to it.
Imagine a world where this 'open' approach gains market share. For the consumer, the net result easily could be that USB, which now is highly plug and play, becomes more like the way ISA cards used to be plug and play: you can plug in any device, but to make it work, you need to do some voodoo (oops, there's more than one device with that PID/VID. Please tell me what you plugged in: X, Y, Z, or something I haven't heard of?")
Exaggeration? Yes, but not completely untrue, and that's the argument I would make.
Whatever you do, you need some entity that prevents multiple manufacturers from using clashing identifiers. That is one of the things the owners of the standard will fight for to maintain, because it is one of the things required to make USB work as well as it does.
Yes, it would be nice if they sold individual VID/PID pairs to hobbyists. But I do not see a legal reason why they would have to do so. Anti-competitive? Maybe, but they will argue that there are thousands of individual vendors in the market.
For the record, this already is pretty common. Lots of keyboards mimic Apple's VID/PID, and tons of controllers use absolutely nonsense VIDs/PIDs (GameStop's mobile controller line, for example).
This idea did not sit well with VTM Group, the people serving as the
management, PR, legal, and membership and licensing department of the
USB Implementers Forum
The hands, the mouth and collector of thoughts cannot be separated from a thing and still be called a whole. Besides even the title says, "USB Implementers Forum Says No to Open Source"I don't know about that. Publishing houses are certainly separate from authors, and record labels from musicians.
Don't underestimate the USB Implementers Forum. Despite its name, it is not an organization of USB users (big and small). They have a direct interest in this matter because:
a) Like every organization, they need to have some source of income. Technically, they're a non-profit organization, but they're also the one who issue the VID, and a company giving out PIDs to whoever wants them is eating their "lack of profit".
b) Its members who have an interest in consumer devices/end products (i.e. companies that don't sell chips, but devices using chips) tend to be large and slow-moving. The Kickstarter crowd is pecking at their business options. (True story).
So if you put the USB logo on your marketing and claim to have a "USB Mini" connector in your specifications then you could be in trouble on two fronts: (1) the usb folks can sue you for using their IP and (2) purchasers can claim the product is not "as described" which may given them certain rights dependent upon the location.
Not using the official logo shouldn't be a problem in hobby market. Everyone will recognise the connector. Not being allowed to identify it as USB2 or USB3 or whatever, that could be a problem. I'm sure there are creative ways around it though.
And about squatting on a VID.. Well, they should have thought about pollution of their namespace on their anti-hobbiest policies. They frankly deserve it.
The most prolific of those 3rd party companies was sued by Nintendo and lost.[1][2] Although that case is not directly applicable, and had different circumstances. I thought it was worth mentioning.
[1] http://digital-law-online.info/cases/24PQ2D1015.htm
[2] http://www.1up.com/do/feature?pager.offset=1&cId=3146206
"Connects to your computer at speeds up to five gigabits per second using industry standard USB cable," probably covers everything short of a the edge cases such as government procurement contracts.
V-USB for AVR gives you 2 VID/PID pairs for 500 Euro. http://www.obdev.at/products/vusb/license.html
There's also a 10EUR hobby package which gives you a pair for personal use only.
FUP applies, but if you're breaking it then really you should go legit and pay the USB feds their protection money.
How are these guys getting round it?
So whether you can safely ignore this depends largely on how easy it is for this body to successfully throw the book at you, and others' success in this area doesn't really mean anything unless you're able to operate in the same circumstances, which I doubt most of us are.
http://www.lettersofnote.com/2012/03/butt-head-astronomer.ht...
"There are a number of ideas to get around VTM Group that include squatting on USB VID 0xF055"
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.
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.
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.
development usb "vid" -video
First hit is someone asking about VID/PID in a motherboard forum.