On Thu, Oct 25, 2001 at 03:38:51AM +0100, Tom Barnes-Lawrence wrote: > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 > P: Vendor=0572 ProdID=1232 Rev= 0.01 > S: Manufacturer=Conexant Systems, Incorporated > S: Product=V.90 modem with USB interface > S: SerialNumber=000000000000000001 > C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 8 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 1ms > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 1ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 1ms > E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 1ms > E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl= 1ms > E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl= 1ms > E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl= 1ms > E: Ad=84(I) Atr=02(Bulk) MxPS= 64 Ivl= 1ms > > Hope it is of use...
That's a vendor specific device. The acm driver will not work with it. > Well, yes, I kind of knew that, but I meant does anyone know if they'd > made that vendor specific protocol backwards compatible with the standard > one -like their serial modem protocol was. Obviously a driver such as ACM > will only respond to devices that *report* that they are ACM devices. But > you can see what I'm asking, right? > Seeing as it is *called* a hardware modem... Who knows. Try asking the vendor for the protocol specs. Or you can try reverse engineering the protocol by sniffing a Windows USB trace of the device in action. Good luck, greg k-h _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
