Yesterday I looked at the modem and, unfortunately, looks like a winmodem.
Because in the winmodem.inf it says:
[USR]
%Winmodem.DeviceDesc% = Winmodem,
PCI\VEN_12B9&DEV_1006&SUBSYS_006012B9&REV_00
and lspci -vvx says:
00:09.0 Communication controller: US Robotics: Unknown device 1006
Subsystem: Unknown device 12b9:0060
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e5018000 (32-bit, prefetchable)
Region 1: Memory at e5000000 (32-bit, prefetchable)
Region 2: Memory at e5010000 (32-bit, prefetchable)
Capabilities: [40] Power Management version 2
Flags: PMEClk- AuxPwr- DSI+ D1- D2+ PME+
Status: D0 PME-Enable- DSel=6 DScale=2 PME-
00: b9 12 06 10 02 00 90 02 00 00 80 07 00 00 00 00
10: 08 80 01 e5 08 00 00 e5 08 00 01 e5 00 00 00 00
20: 00 00 00 00 00 00 00 00 48 00 00 00 b9 12 60 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00
so vendor/device and sub ids match :(
Does one have any ideas on how to proceed? (I suppose I will need some
sort of PCI traffic analyzer for windows or run the driver inside vmware
to learn how it works?)
Regards,
------
Tigran A. Aivazian | http://www.sco.com
Escalations Research Group | tel: +44-(0)1923-813796
Santa Cruz Operation Ltd | http://www.ocston.org/~tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/