In message <20070811225831.GA19654@panix.com>, Thor Lancelot Simon writes:
>I'm trying to use a Startech card with an Oxford OX16PCI952 (dual-port
>16950) with our com driver.  The 16952 is 16650-compatible including,
>according to the datasheet, starting up in 16550 mode.  I am seeing
>characters echoed back to me in 'cu' but not, as far as I can tell,
>transmitted by the device.  I haven't yet rebuilt the driver with the
>COM_16650 option.

A side note on this:  I have a 4-port card based on a closely related
chip, the board made by Siig or some such.  They only support Windows.  Why?
Because there are things that must be done at startup to make the chip
work at all, let alone correctly.  So, for instance, with the (very
functional on real hardware, I understand) 16550 driver in OS X, you can get
some output, but it's at unpredictable near-misses of implausible baud
rates -- I was able to get slightly recognizable output from it by
setting the tty to 57600 and the connected terminal to something around
76800, with a change in number of stop bits.

I would double-check with the data sheet to see whether there's any simple
register hackery that will REALLY put it in compatible mode.

-s