Subject: Re: pci modem
To: Chris G. Demetriou <cgd@netbsd.org>
From: Tom Javen <tomja@InnoTrac.fi>
List: current-users
Date: 12/23/1998 08:14:07
On 21 Dec 1998, Chris G. Demetriou wrote:
> Tom Javen <tomja@InnoTrac.fi> writes:
> > I have a pci modem (commbridge) with Rockwell chipset.
> > puc driver does not recognice the card.
> > The card identifies itself as a communications device , serial.
>
> Sure, but what's the 'interface' reported by the PCI configuration
> header? (should be in your dmesg output, if i'm reading the PCI code
> correctly.)
>
> Last i'd heard, most of those pci modem cards did _not_ present
> themselves as 16x50 serial ports. somebody please clue me in if i'm
> out of date.
>
>
> > Anyone working on attaching a pci serial port as a com port ?
>
> The 'puc' driver does that, but it needs configuration glue (see
> puc_data.c) for each different kind of board. The 'standard' about
> what a PCI serial port is doesn't seem to be followed particularly
> carefully...
>
>
I patched the puc driver to give some information.
src/sys/dev/pci/puc.c
puc_match()
....
if (PCI_CLASS(pa->pa_class) == PCI_CLASS_COMMUNICATIONS &&
PCI_SUBCLASS(pa->pa_class) == PCI_SUBCLASS_COMMUNICATIONS_SERIAL)
return (1);
dmesg:
puc0 at pci0 dev 9 function 0:
PCI configuration registers:
Common header:
0x00: 0x1005127a 0x02900007 0x07000001 0x00002000
Vendor Name: Rockwell Semiconductor Systems (0x127a)
Device Name: (0x1005)
Command register: 0x0007
I/O space accesses: on
Memory space accesses: on
Bus mastering: on
Special cycles: off
MWI transactions: off
Palette snooping: off
Parity error checking: off
Address/data stepping: off
System error (SERR): off
Fast back-to-back transactions: off
Status register: 0x0290
66 MHz capable: off
User Definable Features (UDF) support: off
Fast back-to-back capable: on
Data parity error detected: off
DEVSEL timing: medium (0x1)
Slave signaled Target Abort: off
Master received Target Abort: off
Master received Master Abort: off
Asserted System Error (SERR): off
Parity error detected: off
Class Name: communications (0x07)
Subclass Name: serial (0x00)
Interface: 0x00
Revision ID: 0x01
BIST: 0x00
Header Type: 0x00 (0x00)
Latency Timer: 0x20
Cache Line Size: 0x00
Type 0 ("normal" device) header:
0x10: 0xe5800000 0x00000000 0x00000000 0x00000000
0x20: 0x00000000 0x00000000 0x00008001 0x1005127a
0x30: 0x00000000 0x00000040 0x00000000 0x000001ff
Base address register at 0x10
type: 32-bit noncacheable memory
base: 0xe5800000, size: 0x00010000
Base address register at 0x14
not implemented(?)
Base address register at 0x18
not implemented(?)
Base address register at 0x1c
not implemented(?)
Base address register at 0x20
not implemented(?)
Base address register at 0x24
not implemented(?)
Cardbus CIS Pointer: 0x00008001
Subsystem vendor ID: 0x127a
Subsystem ID: 0x1005
Expansion ROM Base Address: 0x00000000
Reserved @ 0x34: 0x00000040
Reserved @ 0x38: 0x00000000
Maximum Latency: 0x00
Minimum Grant: 0x00
Interrupt pin: 0x01 (pin A)
Interrupt line: 0xff
Device-dependent header:
0x40: 0x48210001 0x00000000 0x00000000 0x00000000
0x50: 0x00000000 0x00000000 0x00000000 0x00000000
0x60: 0x00000000 0x00000000 0x00000000 0x00000000
0x70: 0x00000000 0x00000000 0x00000000 0x00000000
0x80: 0x00000000 0x00000000 0x00000000 0x00000000
0x90: 0x00000000 0x00000000 0x00000000 0x00000000
0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
0xf0: 0x00000000 0x00000000 0x00000000 0x00000000
Don't know how to pretty-print device-dependent header.
Anything more I could try ?
Tom
--
Tom Javen
Innotrac Diagnostics Oy
phone +358-2-2410025 fax +358-2-2410024
gsm +358-40-5860532 email tom.javen@innotrac.fi