Ignore:
Timestamp:
Apr 3, 2000, 3:31:17 PM (21 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Children:
7f02ee73
Parents:
effc2c4
Message:

Enhancements from Charles-Antoine Gauthier <charles.gauthier@…>.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • c/src/tests/libtests/termios/README

    reffc2c4 r33677ef5  
    44
    55These tests are brought to you by the letter `q'.
     6
     7When you start the test, you should see:
     8
     9  You have the following choices:
     10    1 - Reset the struct termios
     11    2 - Look at the current termios setting
     12    3 - Change the line characteristics
     13    4 - Test canonical input
     14    5 - Test raw input
     15    9 - Exit
     16  Enter your choice (1 to 5 or 9, followed by a carriage return):
     17
     18The individual tests are briefly described below:
     19
     20
     211. Reset the struct termios.
     22
     23Included just in case you get into trouble. More than likely, if you are in
     24trouble, neither input nor output are likely to work and this won't help. But
     25hey, it should give you some warm fuzzy feeling that its there...
     26
     27
     282. Look at the current termios setting
     29
     30Dumps the current state of the termios settings in hex and with symbolic flag
     31names.
     32
     33
     343. Change the line characteristics
     35
     36Allows you to change the line speed, parity, number of data bits and number of
     37stop bits. You must supply a delay before the change takes effect. This gives
     38you time to switch your terminal settings to continue with the test.
     39
     40WARNING: Minicom under Linux gets extremely unhappy (as does the /dev/ttyS?
     41underlying devices) if you change the line characteristics and do not make the
     42corresponding change in the terminal emulator.
     43
     44
     454. Test canonical input
     46
     47Simple test of canonical or cooked input mode. Try typing some tabs and/or control characters and make sure that you can backspace over them properly.
     48
     49
     505. Test raw input
     51
     52The line is placed into raw mode and four separate test are done:
    653
    754VMIN=0, VTIME=0
     
    2471VMIN=5, VTIME=20
    2572        Type a character.  Two seconds later a line should be printed.
    26         Count should be 1.  Type a character, and another within 2 
    27 seconds.
    28         Two seconds after last character (or right after the 5th 
    29 character)
     73        Count should be 1.  Type a character, and another within 2 seconds.
     74        Two seconds after last character (or right after the 5th character)
    3075        a line should be printed.
    3176        Type a `q' as the first character of a group to finish the test.
    32        
     77
     78
     799. Exit
     80
     81Gets you out of the test.
     82
     83
    3384Clear???
    3485
    35 Also, when testing the cooked mode input, try typing some tabs 
    36 and/or control characters and make sure that you can backspace over 
    37 them properly.
    3886
    3987---
     
    4492Saskatoon, Canada.
    4593
     94Charles-Antoine Gauthier
     95Software Engineering Group
     96Institute for Information Technology
     97National Research Council of Canada
     98charles.gauthier@nrc.ca
     99
Note: See TracChangeset for help on using the changeset viewer.