Date: Sat, 15 Jan 2000 00:38:37 +0100
From: Martin Mares <mj@suse.cz>
What class and prog-if do these boards use?
Well, here's the lspci -vv for a number of these boards. As you can
see, it's all over the map.
- Ted
This is a Panacom Quadmodem:
00:10.0 Communication controller: Unknown device 14d4:0402 (rev 01)
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 16
Region 0: Memory at febfff80 (32-bit, non-prefetchable)
Region 1: I/O ports at ec00
Region 2: I/O ports at eff0
Region 3: I/O ports at efe0
This is Sealevel systems dual port serial board.
00:11.0 Serial controller: Sealevel Systems Inc: Unknown device 7101 (rev 01) (prog-if 02)
Subsystem: Unknown device 135e:7101
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 17
Region 0: Memory at febfff00 (32-bit, non-prefetchable)
Region 1: I/O ports at e880
Region 2: I/O ports at efa8
This is a USR 3COM #5610.
00:12.0 Serial controller: US Robotics: Unknown device 1008 (rev 01) (prog-if 02)
Subsystem: Unknown device 12b9:00ad
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 18
Region 0: I/O ports at efa0
Capabilities: <available only to root>
-
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/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:17 EST