Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 May 2004 22:51:51 +0400
From:      Roman Kurakin <rik@cronyx.ru>
To:        Marcel Moolenaar <marcel@xcllnt.net>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Sio & Puc memory mapped
Message-ID:  <40A51547.3000000@cronyx.ru>
In-Reply-To: <20040514163718.GA53695@ns1.xcllnt.net>
References:  <40A26162.9030607@cronyx.ru> <20040512.200542.09569104.imp@bsdimp.com> <40A37468.3060608@cronyx.ru> <20040513155109.GB6572@dhcp01.pn.xcllnt.net> <40A4E2CB.2000007@cronyx.ru> <20040514163718.GA53695@ns1.xcllnt.net>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------070903020004050501080102
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Marcel Moolenaar wrote:

>On Fri, May 14, 2004 at 07:16:27PM +0400, Roman Kurakin wrote:
>
>*snip*
>  
>
>>I don't have any other cards supported by uart(4), so I can't test
>>it by my self. If you have a time and ability, I'll send these tests
>>for you.
>>    
>>
>Love to. I can take a look at it this weekend. If the tests aren't
>self-explanatory, could you add a small note about what they are
>supposed to test and if not obvious, what their expected outcome is?
>  
>
If you get an error or test freeze this would be bad.
The only problem that could be - "break test" should fail.
Other tests should pass.

I doesn't use break test, so I put off to find out why this part
is broken.

Usage:
        aiotest [-spmfb] device1 device2
Options:
        -s      speed test
        -p      parity test
        -m      pmodem signals test
        -f      flow control test
        -b      break test

This test tests two ports. You need a full null-mode cable for it.

Usage:
        asytest [-b baud] [-p pattern] device...
Options:
        -b #    data rate, default 115200 bits/sec
        -p [12] pattern, default 1
                 1 0xAA/0x55
                 2 random

This is single port test. You need a loop for it. You may run two tests
for two connected to each other ports, but in that case I would unable
to use random pattern. On linux 2.6 serial driver test with constant
pattern works almost fine, but with random shows how it is buggy.

rik


--------------070903020004050501080102--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40A51547.3000000>