Earlier quoted context omitted.
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"
The article is a second-hand source; the author could be trying to stir something up, or maybe just got a bit too excited. Who knows? The article also says the proposal, among others, "haven’t hit the desk of anyone at the USB Implementers Forum, the people who are actually in charge of designating USB VIDs and PIDs". Doesn't sound like the forum said no to me.
USB Implementers Forum Says No to Open Source
71–80 of 100 posts
Re: USB Implementers Forum Says No to Open Source
#72Why not just pick a VID and start using it? USB is so well understood at this point that there is no need for anyone to play ball with an "official" organization. (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.)
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 perfec…
Re: USB Implementers Forum Says No to Open Source
#73Earlier quoted context omitted.
Wow. If you tought a memory stick pretending that it's a keyboard was a serious enough problem, just wait untill somebody thinks loading random drivers from the device (or the web!) is a good idea. It will happen, that's a near certainty. Some day, somebody will think that's a good idea, and since it's easy, the scheme will get widely used.
If you don't trust the web or the device, where will you get the driver? Why did you plug the device in the first place?
Whether this is actually better probably depends on your point of view. But loading (somehow OS-neutral?) drivers from a fixed store on the device seems like a great way to be stuck with out-of-date binary blobs forever.
Re: USB Implementers Forum Says No to Open Source
#74If they can't responsibly offer their product without revoking it for simply using it as intended, they are racketeers. The Open Source community has not broken any legal agreements in simply publicizing the idea of a shared VID. The USB Forum are completely in the wrong for their behavior.
Re: USB Implementers Forum Says No to Open Source
#75Earlier quoted context omitted.
That's the humorous part of the whole discussion that the VTM group is trying to preserve revenue by ignoring the hobbyists and sticking with the people who think nothing of falsifying UL registry, falsifying FCC certifications, and violating patents, but I'm sure those guys would never turn against the VTM group and illegally use the USB trademark without permission, LOL. Whereas the hobbyists, if you don't intentio…
> Legendarily it was HP (or was it sun?) who shipped a whole batch of ethernet cards accidentally in the 90s with the same MAC address, boy was that a nightmare to figure out the hard way. Sun used to use the same MAC address on each port of their QFE (quad fast Ethernet) cards. It was easy to fix with ifconfig, but always made me wonder two things: a) if I number these ports sequentially (:a, :b, ...) am I going to…
Re: USB Implementers Forum Says No to Open Source
#76Why not just pick a VID and start using it? USB is so well understood at this point that there is no need for anyone to play ball with an "official" organization. (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.)
The way these things normally work is that you're only allowed to use the name and marks if you're an official licensee. 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 right…
Re: USB Implementers Forum Says No to Open Source
#77Earlier quoted context omitted.
They have: "There are a number of ideas to get around VTM Group that include squatting on USB VID 0xF055"
Does 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.
Re: USB Implementers Forum Says No to Open Source
#78Earlier quoted context omitted.
Let's just call it ThatThing2 and ThatThing3 in the hobby community :P
How about BSU? It could stand for a lot of things... but I like Bull Sh!t USB. Which I think is an appropriate eye-poke response to an annoying organization.
http://www.lettersofnote.com/2012/03/butt-head-astronomer.ht...
Re: USB Implementers Forum Says No to Open Source
#79Earlier quoted context omitted.
Nothing is stopping anyone from using any given VID for their own purposes of testing. If its in your own garage as the article mentions, you can use whatever you want. However, once it's out in the wild (even if it's just the few hundred devices), the USB-IF (and their lawyers) apparently can squash it. The fee is $5k if I recall. As others have mentioned, if you are planning on making a real product, it's something…
Technically, you could, but you don't want to stomp on other vendor's feet. It's a bit like mac addresses or IP addresses, you can do what you want but you probably want to behave in society (in the case of IP addresses, you'll need friends for routing). And also, to find the device from the OS API, you sometimes have to submit the VID/PID of the device you are looking for. Example: http://developer.chrome.com/apps/u…
Re: USB Implementers Forum Says No to Open Source
#80Earlier quoted context omitted.
If you don't trust the web or the device, where will you get the driver? Why did you plug the device in the first place?
Perhaps the Linux kernel you already have installed, which presently has drivers for just about everything included and developed in a centralized, controlled fashion... Whether this is actually better probably depends on your point of view. But loading (somehow OS-neutral?) drivers from a fixed store on the device seems like a great way to be stuck with out-of-date binary blobs forever.