Oxford Semiconductor's OXCB950 UART not recognized by serial. c

Oxford Semiconductor's OXCB950 UART not recognized by serial. c

Post by fabrizio.genn.. » Sat, 02 Mar 2002 04:40:13



Ed, you are right, the card matches the entry before the last one in
serial_pci_tbl[], the one with PCI_ANY_ID for both vendor and device. So I
would like to add an entry in serial_pci_tbl[] for the vendor
PCI_VENDOR_ID_OXSEMI and device 950b. However I do not know what to put in
the field driver_data. Probably pbn_b0_1_115200 would be fine, but this is
the default, so serial_init_one would try to call serial_pci_guess_board,
but this fails...

Fabrizio Gennari
Philips Research Monza
via G.Casati 23, 20052 Monza (MI), Italy
tel. +39 039 2037816, fax +39 039 2037800


21/02/2002 01.05




        Subject:        RE: Oxford Semiconductor's OXCB950 UART not recognized by serial.       c
        Classification:


> We have 32-bit CardBus cards with OXCB950 CardBus (PCI ID 1415:950b)
UART
> chips on them (OXCB950 is the CardBus version of 16C950) . The module
> serial_cb in the pcmcia-cs package recognizes them correctly. But, when
> not using serial_cb, the function serial_pci_guess_board in serial.c
> doesn't (kernel 2.4.17 tested). The problem is that the card advertises
3
> i/o memory regions and 2 ports. If one replaces the line

> if (num_iomem <= 1 && num_port == 1) {

> with

> if (num_port >= 1) {

> in the function serial_pci_guess_board(), the card is detected and works
> perfectly. Only, when inserting it, the kernel displays the message:

> Redundant entry in serial pci_table.  Please send the output of
> lspci -vv, this message (1415,950b,1415,0001)
> and the manufacturer and name of serial board or modem board


The "Redundant entry" message comes out of serial.c when a card is found
in
the PCI ID board list, but which function serial_pci_guess_board() also
detects as a generic single UART card (and overwrites the card's
board->flags field in the pci_boards[] array).

Does anybody think this is a feature? Did I misunderstand?

I suspect that the thought was to detect and eventually remove
pci_boards[]
entries for generic single-port cards that could also be detected by the
serial_pci_guess_board() function. Can anybody confirm or deny?

Shouldn't the detection process be considered done when the PCI IDs match?
Why should the "guess" function even be called when the card has already
been found in the PCI board table?

----------------------------------------------------------------

Macrolink, Inc.       1500 N. Kellogg Dr  Anaheim, CA  92807
----------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. Oxford Semiconductor's OXCB950 UART not recognized by serial.c

We have 32-bit CardBus cards with OXCB950 CardBus (PCI ID 1415:950b) UART
chips on them (OXCB950 is the CardBus version of 16C950) . The module
serial_cb in the pcmcia-cs package recognizes them correctly. But, when
not using serial_cb, the function serial_pci_guess_board in serial.c
doesn't (kernel 2.4.17 tested). The problem is that the card advertises 3
i/o memory regions and 2 ports. If one replaces the line

if (num_iomem <= 1 && num_port == 1) {

with

if (num_port >= 1) {

in the function serial_pci_guess_board(), the card is detected and works
perfectly. Only, when inserting it, the kernel displays the message:

Redundant entry in serial pci_table.  Please send the output of
lspci -vv, this message (1415,950b,1415,0001)
and the manufacturer and name of serial board or modem board

And this is the output of lspci -vv, only the part relevant to the Oxford
card:

03:00.0 Serial controller: Oxford Semiconductor Ltd CardBus Device
(prog-if 06 [16950])
        Subsystem: Oxford Semiconductor Ltd: Unknown device 0001
        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: I/O ports at 4800 [size=8]
        Region 1: Memory at 10c00000 (32-bit, non-prefetchable) [size=4K]
        Region 2: I/O ports at 4810 [size=16]
        Region 3: Memory at 10c01000 (32-bit, non-prefetchable) [size=4K]
        Region 4: Memory at 10c02000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 1
                Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA
PME(D0+,D1-,D2+,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Fabrizio Gennari
Philips Research Monza
via G.Casati 23, 20052 Monza (MI), Italy
tel. +39 039 2037816, fax +39 039 2037800
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. C.O.L.A. Newcomer FAQ and Primer - Edition: 6 - 5/03/02

3. OXCB950 support (was RE: Oxford Semiconductor's OXCB950 UART not recognized by serial. c)

4. How to install driver from floppy disk

5. Oxford Semiconductor's OXCB950 UART not recognized by serial. c

6. ip masqing

7. malloc problem with libc.so

8. PCI-Printerport Oxford-Semiconductors

9. Problem to use a Oxford semiconductor Intelligent DUAL Channe l UA RT (OX16PCI952)

10. Using an Oxford Semiconductor 840 Parport

11. Problem to use a Oxford semiconductor Intelligent DUAL Channe l UA RT (OX16PCI952)

12. PCI device ID Oxford 952 UART