On Mon, May 17, 2010 at 02:13:16PM +0300, Matti Aarnio wrote: > On Sun, May 16, 2010 at 05:48:09PM -0700, Greg KH wrote: > > On Mon, May 17, 2010 at 02:05:27AM +0300, Matti Aarnio wrote: > > > Hi, > > > > > > People are aware of FTDI's FT232 serial port chips, and FT245 printer port > > > chips, but they are actually more generic devices. There are serial port devices, > > > and there are generic FIFO devices. (www.ftdichip.com) > > > > > > Worst of all, they all use default ID pair 0403:6001, which is now handled by > > > the ftdi_sio driver. (Dual and quad versions have different IDs, handled by > > > same driver - lattest bunch has very peculiar capabilities: JTAG, and SPI on > > > serial port, same pins also serve as generic data FIFO...) > > > Unfortunately a non-zero number of vendors are outputing hardware that use > > > the hardware default ID pair :-( > > > > > > A distinguisher in between the devices with same ID codes could be USB device > > > descriptor's iProduct string. That one is usually defined by the hardware > > > vendor to be their actual product name. > > > > > > This relates to recent _audio_device_ case, where device maker apparently has > > > used FTDI FIFO chip, and then just hacked things at Windows driver for it. > > > > Ugh, you are kidding me. That's just horrible :( > > You wish... I happen to have hardware that behaves like this. > I do have even an old Linux driver for it. > (Getting it to compile on modern Linux was a bit of work in itself..) > > http://ham.zmailer.org/oh2mqk/linux-sdriq-usb-driver.c > > Source for the driver is on Linrad package, which is GPL licensed, but > getting sign-offs from original authors may not be easy... > > "lsusb -v" output is at the end of this email. Wow, what a mess (that driver, and the device...) Anyway, I'll gladly take a patch to the ftdi_sio driver to not bind to this device to make it easier for users of this hardware. 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
