I have a bike computer with a USB cradle and the obligatory crap windows app. Didn't bother with it much but discovered there is an open source bike monitoring app with download for lots of different hardware (Golden Cheetah). But it doesn't support the VDO Z3. The hardware shows up as a Megawin USB serial bridge. There is a datasheet online, and looks like others have fiddled with it in the past. Is there anything wrong with just making a stub wrapper that calls the usb generic driver, or is it better to just add more ID's to the existing driver? http://www.megawin.com.tw/megawin_EN/ProductShow.asp?ID=178 Bus 002 Device 008: ID 0e6a:0101 Megawin Technology Co., Ltd MA100 [USB-UART Bridge IC] Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0e6a Megawin Technology Co., Ltd idProduct 0x0101 MA100 [USB-UART Bridge IC] bcdDevice 5.10 iManufacturer 0 iProduct 2 USB Bridge iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x0000 (Bus Powered) -- 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
