On Wed, May 19, 2010 at 10:23:30AM -0600, R. Steve McKown wrote: > On Tuesday 18 May 2010 08:01:09 pm you wrote: > > On Tue, May 18, 2010 at 04:57:37PM -0600, Steve McKown wrote: > > > On Tuesday 18 May 2010 08:55:39 am Greg KH wrote: > > > > On Tue, May 18, 2010 at 08:44:59AM -0600, Steve McKown wrote: > > > > - Set VID, PID and descriptors: product, serial, and device version. > > > > You can dynamically change the vid and pid and stuff? Heh, that's going > > to be fun to track :) > > Thankfully it takes some work to get valid VID/PID allocations, so I don't > suspect a rash of new ones as a result of this driver. We just use the > default VID/PID, even though we've toyed with getting our own. Oh, you have not seen what people do in the real world. I have a bunch of devices here with a vid/pid of 0x0000/0x0000. And those are devices you can go buy from the store today... Lots of companies set these fields to random values, do you really want to make it easier for them to do this? :) But also note that we have a valid VID that we use for Linux-based devices to assign PIDs for, so it isn't really that hard to get a valid VID these days... thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html