serial card on RC2 , RC3

[Conall O'Brien]

On 27 December 2013 19:13, Milan Obuch <freebsd-stable at dino.sk> wrote:
> On Fri, 27 Dec 2013 13:41:50 -0500 (EST)
> Darrel <levitch at iglou.com> wrote:
>
>>
>> >> Anyone know how to get serial cable working with StarTech "2 Port
>> >> Native Express RS232 Serial Adapter Card with 16550 UART"?  It is
>> >> part number PEX2S553.

I've been trying to get the low profile version (part PEX2S553LP) of
this card to work in my system on and off for a while now.


Having added the following diff (which I keep meaning to submit in a
PR), I have the uart driver recognising the card.

--- sys/dev/uart/uart_bus_pci.c (revision 259948)
+++ sys/dev/uart/uart_bus_pci.c (working copy)
@@ -130,6 +130,8 @@
        "MosChip MCS9901 PCIe to Peripheral Controller", 0x10 },
 { 0x9710, 0x9904, 0xa000, 0x1000,
        "MosChip MCS9904 PCIe to Peripheral Controller", 0x10 },
+{ 0x9710, 0x9922, 0xa000, 0x1000,
+       "MosChip MCS9900 PCIe to Peripheral Controller", 0x10 },
 { 0xdeaf, 0x9051, 0xffff, 0, "Middle Digital PC Weasel Serial Port", 0x10 },
 { 0xffff, 0, 0xffff, 0, NULL, 0, 0}
 };

grep uart /var/run/dmesg.boot:

uart2: <Non-standard ns8250 class UART with FIFOs> port 0xd010-0xd017
mem 0xfe203000-0xfe203fff,0xfe202000-0xfe202fff irq 18 at device 0.0
on pci4
uart3: <Non-standard ns8250 class UART with FIFOs> port 0xd000-0xd007
mem 0xfe201000-0xfe201fff,0xfe200000-0xfe200fff irq 19 at device 0.1
on pci4

and with pciconf -lv

uart2 at pci0:4:0:0:       class=0x070002 card=0x1000a000 chip=0x99229710
rev=0x00 hdr=0x00
    vendor     = 'NetMos Technology'
    device     = 'PCIe 9922 Multi-I/O Controller'
    class      = simple comms
    subclass   = UART
uart3 at pci0:4:0:1:       class=0x070002 card=0x1000a000 chip=0x99229710
rev=0x00 hdr=0x00
    vendor     = 'NetMos Technology'
    device     = 'PCIe 9922 Multi-I/O Controller'
    class      = simple comms
    subclass   = UART


However, I can't get a working tty on either serial port. When I
connect over the serial port, I have a blank tty, which clearly states
"Not a controlling terminal" when sent SIGINFO.

>> >> In my kernel I tried this:
>> >>
>> >> device puc
>> >> device sio
>> >> options COM_MULTIPORT
>> >>
>> >> in different variations.
>> >>
>> >> Also I tried in /boot/device.hints:
>> >>
>> >> hint.sio.2.flags="0x201"
>> >> hint.sio.3.flags="0x201"
>> >>
>> >> It is obviously a cheap card, but I do have one working in a msft
>> >> 7 machine.
>> >>
>> >
>> > Please post some more information about your system.  pciconf -lv
>> > and dmesg would both help developers see why the card isn't
>> > detected.  If your system has been up for a while you may be better
>> > off sending /var/run/dmesg.boot than the output of the dmesg
>> > program.
>> >
>>
>
> Hi,
>
> could you apply following patch to /usr/src/sys/dev/puc/pucdata.c and
> rebuild your kernel and/or modules? This is the first thing I would
> test, and it could even work, but no guarantee yet, naturally :)

> --- pucdata.c   2013-10-23 22:51:08.000000000 +0200
> +++ pucdata.c.mod       2013-12-27 20:09:36.000000000 +0100
> @@ -1094,6 +1094,12 @@
>             PUC_PORT_2P, 0x10, 4, 0,
>         },
>
> +       {   0x9710, 0x9922, 0xffff, 0,
> +           "NetMos NM9922 Dual UART",
> +           DEFAULT_RCLK,
> +           PUC_PORT_2S, 0x10, 4, 0,
> +       },
> +
>         {   0xb00c, 0x021c, 0xffff, 0,
>             "IC Book Labs Gunboat x4 Lite",
>             DEFAULT_RCLK,

I'm currently trying to enable sio, but run into kernel compile time
problems already reported in
http://www.freebsd.org/cgi/query-pr.cgi?pr=166626 . Perhaps I need to
give up on sio and try using the puc driver with your patch

> [ dmesg and pciconf output snipped ]
>
> Regards,
> Milan
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"



-- 

Conall O'Brien