1.\" Copyright (c) 1986, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" %sccs.include.redist.man% 5.\" 6.\" @(#)vx.4 8.1 (Berkeley) 06/05/93 7.\" 8.Dd 9.Dt VX 4 tahoe 10.Os 11.Sh NAME 12.Nm vx 13.Nd 14.TN VIOC-X 15communications multiplexor 16.Sh SYNOPSIS 17.Cd "device vx0 at vba? csr 0xfffe0000 vector vackint vcmdrsp vunsol" 18.Sh DESCRIPTION 19A 20.Tn VIOC-X 21provides 16 communication lines with partial modem control, 22adequate for 23.Tn UNIX 24dialup use. 25and may be set to run at any of 16 speeds; see 26.Xr tty 4 . 27.Sh FILES 28.Bl -tag -width /dev/tty[0-9][0-9]xx -compact 29.It Pa /dev/tty[0-9][0-9] 30.It Pa /dev/ttyd[0-9a-f] 31dialups 32.El 33.Sh DIAGNOSTICS 34.Bl -diag 35.It vx%d: vc proc err, ustat %x. 36.Pp 37.It vx%d: vc uqual err, uqual %x. 38.Pp 39.It vx%d: %d exceeds silo size. 40.Pp 41.It vx%d: receiver overrun. 42.Pp 43.It VIOC-BOP no. %d at %x. 44The system identified a vioc supporting the bit oriented protocol. 45The number 46.Em %d 47is the board number assigned by the system 48while the address 49.Em %x 50is the address of the command control 51block for the vioc. 52.It vx%d: unknown type %x. 53The system encountered a vioc of unknown type during autoconfiguration. 54.It vx%d: didn't respond to LIDENT. 55The device did not respond to the configuration command that 56sets the interrupt vectors and port configuration. 57.It vx%d: %s%s, ports %d-%d. 58This is informatory message printed during autoconfiguration 59indicating the type of hardware present the port configuration. 60.It vx%d: no buffers. 61All the command buffers were in use; this indicates the device 62is constipated for some reason. 63.It vx%d: setq overflow. 64An attempt to append a command to an existing command buffer 65failed because the buffer was full or the hardware doesn't 66support this facility. 67.It vx%d: cmd q overflow. 68An attempt to place a new command on the command queue failed 69because it was full. The device is either overloaded or hung 70up for some reason. If this happens, the system tries to 71reset the device to unwedge it. 72.It vx%d INTR ERR type %x v_dcd %x. 73An error was returned by the device in response to some command. 74The command identifier and data carrier detect mask are printed 75followed by the contents of the command buffer in error. 76.It vx%d: vcmdrsp interrupt. 77A command response interrupt was received from a bop (bit oriented 78protocol) vioc. This should not happen. 79.It vx%d: cmdresp debug. 80.Pp 81.It vx%d: vunsol from 82.Tn BOP . 83An unsolicited interrupt was received from a bop vioc. This should 84not happen. 85.It vx%d: interrupt q overflow. 86The queue of pending interrupts to be delivered to the vioc is 87full. This is probably due to the vioc being wedged. The system 88resets the vioc if this occurs. 89.It vx%d: reset.... 90The system attempted to reset the vioc. 91.El 92.Sh SEE ALSO 93.Xr tty 4 94.Sh HISTORY 95The 96.Nm 97special file appeared in 98.Bx 4.3 tahoe . 99