Hi,
I was pleasantly surprised to see that puc(4) in 8-stable recognizes my
8 port serial cards and identifies them as follows:
puc0: <Timedia technology 8 Port Serial> port
0xe500-0xe51f,0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f,0xe540-0xe547,0xe548-0xe54f
irq 10 at device 14.0 on pci0
puc0: [FILTER]
uart2: <16550 or compatible> on puc0
uart2: [FILTER]
uart3: <Non-standard ns8250 class UART with FIFOs> on puc0
uart3: [FILTER]
uart4: <Non-standard ns8250 class UART with FIFOs> on puc0
uart4: [FILTER]
uart5: <Non-standard ns8250 class UART with FIFOs> on puc0
uart5: [FILTER]
uart6: <Non-standard ns8250 class UART with FIFOs> on puc0
uart6: [FILTER]
uart7: <Non-standard ns8250 class UART with FIFOs> on puc0
uart7: [FILTER]
uart8: <Non-standard ns8250 class UART with FIFOs> on puc0
uart8: [FILTER]
uart9: <Non-standard ns8250 class UART with FIFOs> on puc0
uart9: [FILTER]
The first two ports work correctly but the baudrate of the other six
is incorrect, i.e. I have to use 'tip -76800 uart5' to get the port
to communicate at 9600 baud. I 'know' that this particular hardware
has a baudrate multiplier on the first two ports but not on the other
six.
In pucdata.c I see:
{ 0x1409, 0x7168, 0xffff, 0,
NULL,
DEFAULT_RCLK * 8,
PUC_PORT_NONSTANDARD, 0x10, -1, -1,
.config_function = puc_config_timedia
},
which suggests all ports have the same clock multiplier.
I do not understand enough about the working of the puc driver to see
where this multiplier is looked up per port. Back in 2007 I managed
to get this card to work on FB 6.2 bij changing the puc driver but it
had a separate config line per port at that time.
Hopefully someone can help me to fix this last glitch that keeps me
from upgrading my terminal servers to 8-stable.
Regards,
Paul Schenkeveld