Greg KH wrote:

 >>Using the ACM driver, it is not recognised, and it is listed as
 >>being the "Vendor-supplied driver" type, and uses
 >>(vend/prod 0x572/0x1232). I've looked at various sites,
 >>but not found much out.
 >What is the output of /proc/bus/usb/devices with the device plugged in.

Well, FWIW:

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB UHCI Root Hub
S:  SerialNumber=d400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
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...

 >>Now, I know that (most) software modems aren't supported under
 >>linux, BUT: Rockwell's chipsets for *serial* modems use the
 >>software drivers just to do data compression, and if you try to
 >>use them as plain serial modems, they then work fine, but without
 >>the data compression.
 >If the manufacturer doesn't make their device to match the USB published
 >specs, then they are using a vendor specific protocol.  You need to
 >either get that protocol from the vendor or reverse engineer it to get a
 >driver for Linux.
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...

Thanks,
  Tom Barnes-Lawrence

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to