Commit | Line | Data |
---|---|---|
85b19e5d WJ |
1 | .\" Copyright (c) 1986, 1991 Regents of the University of California. |
2 | .\" All rights reserved. | |
3 | .\" | |
4 | .\" Redistribution and use in source and binary forms, with or without | |
5 | .\" modification, are permitted provided that the following conditions | |
6 | .\" are met: | |
7 | .\" 1. Redistributions of source code must retain the above copyright | |
8 | .\" notice, this list of conditions and the following disclaimer. | |
9 | .\" 2. Redistributions in binary form must reproduce the above copyright | |
10 | .\" notice, this list of conditions and the following disclaimer in the | |
11 | .\" documentation and/or other materials provided with the distribution. | |
12 | .\" 3. All advertising materials mentioning features or use of this software | |
13 | .\" must display the following acknowledgement: | |
14 | .\" This product includes software developed by the University of | |
15 | .\" California, Berkeley and its contributors. | |
16 | .\" 4. Neither the name of the University nor the names of its contributors | |
17 | .\" may be used to endorse or promote products derived from this software | |
18 | .\" without specific prior written permission. | |
19 | .\" | |
20 | .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND | |
21 | .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE | |
22 | .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE | |
23 | .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE | |
24 | .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL | |
25 | .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS | |
26 | .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) | |
27 | .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT | |
28 | .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY | |
29 | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | |
30 | .\" SUCH DAMAGE. | |
31 | .\" | |
32 | .\" @(#)vx.4 6.3 (Berkeley) 3/27/91 | |
33 | .\" | |
34 | .Dd March 27, 1991 | |
35 | .Dt VX 4 tahoe | |
36 | .Os | |
37 | .Sh NAME | |
38 | .Nm vx | |
39 | .Nd | |
40 | .TN VIOC-X | |
41 | communications multiplexor | |
42 | .Sh SYNOPSIS | |
43 | .Cd "device vx0 at vba? csr 0xfffe0000 vector vackint vcmdrsp vunsol" | |
44 | .Sh DESCRIPTION | |
45 | A | |
46 | .Tn VIOC-X | |
47 | provides 16 communication lines with partial modem control, | |
48 | adequate for | |
49 | .Tn UNIX | |
50 | dialup use. | |
51 | and may be set to run at any of 16 speeds; see | |
52 | .Xr tty 4 . | |
53 | .Sh FILES | |
54 | .Bl -tag -width /dev/tty[0-9][0-9]xx -compact | |
55 | .It Pa /dev/tty[0-9][0-9] | |
56 | .It Pa /dev/ttyd[0-9a-f] | |
57 | dialups | |
58 | .El | |
59 | .Sh DIAGNOSTICS | |
60 | .Bl -diag | |
61 | .It vx%d: vc proc err, ustat %x. | |
62 | .Pp | |
63 | .It vx%d: vc uqual err, uqual %x. | |
64 | .Pp | |
65 | .It vx%d: %d exceeds silo size. | |
66 | .Pp | |
67 | .It vx%d: receiver overrun. | |
68 | .Pp | |
69 | .It VIOC-BOP no. %d at %x. | |
70 | The system identified a vioc supporting the bit oriented protocol. | |
71 | The number | |
72 | .Em %d | |
73 | is the board number assigned by the system | |
74 | while the address | |
75 | .Em %x | |
76 | is the address of the command control | |
77 | block for the vioc. | |
78 | .It vx%d: unknown type %x. | |
79 | The system encountered a vioc of unknown type during autoconfiguration. | |
80 | .It vx%d: didn't respond to LIDENT. | |
81 | The device did not respond to the configuration command that | |
82 | sets the interrupt vectors and port configuration. | |
83 | .It vx%d: %s%s, ports %d-%d. | |
84 | This is informatory message printed during autoconfiguration | |
85 | indicating the type of hardware present the port configuration. | |
86 | .It vx%d: no buffers. | |
87 | All the command buffers were in use; this indicates the device | |
88 | is constipated for some reason. | |
89 | .It vx%d: setq overflow. | |
90 | An attempt to append a command to an existing command buffer | |
91 | failed because the buffer was full or the hardware doesn't | |
92 | support this facility. | |
93 | .It vx%d: cmd q overflow. | |
94 | An attempt to place a new command on the command queue failed | |
95 | because it was full. The device is either overloaded or hung | |
96 | up for some reason. If this happens, the system tries to | |
97 | reset the device to unwedge it. | |
98 | .It vx%d INTR ERR type %x v_dcd %x. | |
99 | An error was returned by the device in response to some command. | |
100 | The command identifier and data carrier detect mask are printed | |
101 | followed by the contents of the command buffer in error. | |
102 | .It vx%d: vcmdrsp interrupt. | |
103 | A command response interrupt was received from a bop (bit oriented | |
104 | protocol) vioc. This should not happen. | |
105 | .It vx%d: cmdresp debug. | |
106 | .Pp | |
107 | .It vx%d: vunsol from | |
108 | .Tn BOP . | |
109 | An unsolicited interrupt was received from a bop vioc. This should | |
110 | not happen. | |
111 | .It vx%d: interrupt q overflow. | |
112 | The queue of pending interrupts to be delivered to the vioc is | |
113 | full. This is probably due to the vioc being wedged. The system | |
114 | resets the vioc if this occurs. | |
115 | .It vx%d: reset.... | |
116 | The system attempted to reset the vioc. | |
117 | .El | |
118 | .Sh SEE ALSO | |
119 | .Xr tty 4 | |
120 | .Sh HISTORY | |
121 | The | |
122 | .Nm | |
123 | special file appeared in | |
124 | .Bx 4.3 tahoe . |