From: "Craig Schlenter" <[EMAIL PROTECTED]>
> 0x0002 should be replaced by PCI_DEVICE_ID_DCI_PCCOM8 with
> #define PCI_DEVICE_ID_DCI_PCCOM8 0x0002
> in pci.h (pci_ids.h?) or something but then people without updated
> pci.h are in trouble - perhaps use a #ifdef PCI_DEVICE_ID_DCI_PCCOM8
> so driver will still compile on older kernel/pci.h versions? Yukky
> either way.
This is what serial_compat.h is for. Check in there and you will
see that the Connect Tech PCI IDs are setup if they don't
already exist. You should do the same.
If you didn't explicitly mean the subsystem and subvendor slots
to be PCI_ANY_ID, then you should use lspci -v to find out
what values those are and use them.
> Apparently you can jumper the card to do 400K instead of 115K in
> which case the max baud speed will need to be tuned.
There's a simple hack: Put the uart into loopback mode. Fill up
the fifo and time the transmit. Figure the baud rate from the
time it took to transmit the chars. size_fifo() already does
everything except the timing.
> PS. Decision have their own patches on their website against
> significantly older versions of serial.c which don't have the nifty
> generic pci functions. Those patches do support cards other than the
> PCCOM8. I've ported those patches to 2.2.16's serial.c if anyone wants
> a copy. Available under the no warranty, no support, "works for me but
> may eat your hard drive or do other nasty things" licence of course ...
In the spirit of world domination, all info gleaned should go
into the driver. :-) Send them on. You might also want to
contact the company and mention "Oh BTW in my spare
time I hacked a driver for your boards."
..Stu
-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to [EMAIL PROTECTED]
