1 | # |
---|
2 | # $Id$ |
---|
3 | # |
---|
4 | |
---|
5 | These tests are brought to you by the letter `q'. |
---|
6 | |
---|
7 | When 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 | |
---|
18 | The individual tests are briefly described below: |
---|
19 | |
---|
20 | |
---|
21 | 1. Reset the struct termios. |
---|
22 | |
---|
23 | Included just in case you get into trouble. More than likely, if you are in |
---|
24 | trouble, neither input nor output are likely to work and this won't help. But |
---|
25 | hey, it should give you some warm fuzzy feeling that its there... |
---|
26 | |
---|
27 | |
---|
28 | 2. Look at the current termios setting |
---|
29 | |
---|
30 | Dumps the current state of the termios settings in hex and with symbolic flag |
---|
31 | names. |
---|
32 | |
---|
33 | |
---|
34 | 3. Change the line characteristics |
---|
35 | |
---|
36 | Allows you to change the line speed, parity, number of data bits and number of |
---|
37 | stop bits. You must supply a delay before the change takes effect. This gives |
---|
38 | you time to switch your terminal settings to continue with the test. |
---|
39 | |
---|
40 | WARNING: Minicom under Linux gets extremely unhappy (as does the /dev/ttyS? |
---|
41 | underlying devices) if you change the line characteristics and do not make the |
---|
42 | corresponding change in the terminal emulator. |
---|
43 | |
---|
44 | |
---|
45 | 4. Test canonical input |
---|
46 | |
---|
47 | Simple 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 | |
---|
50 | 5. Test raw input |
---|
51 | |
---|
52 | The line is placed into raw mode and four separate test are done: |
---|
53 | |
---|
54 | VMIN=0, VTIME=0 |
---|
55 | Each letter you type should produce a line of output. |
---|
56 | The `count' should be quite large, since (as you correctly |
---|
57 | pointed out) the read is non-blocking. The time should be |
---|
58 | the interval between typing characters. |
---|
59 | Type a `q' to finish the test. |
---|
60 | VMIN=0, VTIME=20 |
---|
61 | Again, each letter should produce a line of output. The |
---|
62 | `count' should be much smaller -- the read is non-blocking |
---|
63 | but has a timeout of 2 seconds, so the count should be about |
---|
64 | half the `interval'. |
---|
65 | Type a `q' to finish the test. |
---|
66 | VMIN=5, VTIME=0 |
---|
67 | A line should be produced for every 5 characters typed. The |
---|
68 | count should be 1. This is a blocking read. |
---|
69 | Type a `q' as the first character of a group of 5 to finish |
---|
70 | the test. |
---|
71 | VMIN=5, VTIME=20 |
---|
72 | Type a character. Two seconds later a line should be printed. |
---|
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) |
---|
75 | a line should be printed. |
---|
76 | Type a `q' as the first character of a group to finish the test. |
---|
77 | |
---|
78 | |
---|
79 | 9. Exit |
---|
80 | |
---|
81 | Gets you out of the test. |
---|
82 | |
---|
83 | |
---|
84 | Clear??? |
---|
85 | |
---|
86 | |
---|
87 | --- |
---|
88 | Eric Norum |
---|
89 | eric@skatter.usask.ca |
---|
90 | Saskatchewan Accelerator Laboratory |
---|
91 | University of Saskatchewan |
---|
92 | Saskatoon, Canada. |
---|
93 | |
---|
94 | Charles-Antoine Gauthier |
---|
95 | Software Engineering Group |
---|
96 | Institute for Information Technology |
---|
97 | National Research Council of Canada |
---|
98 | charles.gauthier@nrc.ca |
---|
99 | |
---|