Return to vx.4 CVS log

Up to [CSRG BSD Unix] / 43BSDReno / share / man / man4 / man4.tahoe

Annotation of 43BSDReno/share/man/man4/man4.tahoe/vx.4, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1986 Regents of the University of California.
                      2: .\" All rights reserved.  The Berkeley software License Agreement
                      3: .\" specifies the terms and conditions for redistribution.
                      4: .\"
                      5: .\"    @(#)vx.4        6.2 (Berkeley) 6/30/87
                      6: .\"
                      7: .TH VX 4 "June 30, 1987"
                      8: .UC 7
                      9: .SH NAME
                     10: vx \- VIOC-X communications multiplexor
                     11: .SH SYNOPSIS
                     12: .B "device vx0 at vba? csr 0xfffe0000 vector vackint vcmdrsp vunsol"
                     13: .SH DESCRIPTION
                     14: A VIOC-X provides 16 communication lines with partial modem control,
                     15: adequate for UNIX dialup use.
                     16: Each line attached to the VIOC-X communications multiplexor
                     17: behaves as described in
                     18: .IR tty (4)
                     19: and may be set to run at any of 16 speeds; see
                     20: .IR tty (4)
                     21: for the encoding.
                     22: .SH FILES
                     23: /dev/tty[0-9][0-9]
                     24: .br
                     25: /dev/ttyd[0-9a-f]              dialups
                     26: .SH "SEE ALSO"
                     27: tty(4)
                     28: .SH DIAGNOSTICS
                     29: \fBvx%d: vc proc err, ustat %x\fP.
                     30: .PP
                     31: \fBvx%d: vc uqual err, uqual %x\fP.
                     32: .PP
                     33: \fBvx%d: %d exceeds silo size\fP.
                     34: .PP
                     35: \fBvx%d: receiver overrun\fP.
                     36: .PP
                     37: \fBVIOC-BOP no. %d at %x\fP.
                     38: The system identified a vioc supporting the bit oriented protocol.
                     39: The number \fB%d\fP is the board number assigned by the system
                     40: while the address \fB%x\fP is the address of the command control
                     41: block for the vioc.
                     42: .PP
                     43: \fBvx%d: unknown type %x\fP.
                     44: The system encountered a vioc of unknown type during autoconfiguration.
                     45: .PP
                     46: \fBvx%d: didn't respond to LIDENT\fP.
                     47: The device did not respond to the configuration command that
                     48: sets the interrupt vectors and port configuration.
                     49: .PP
                     50: \fBvx%d: %s%s, ports %d-%d\fP.
                     51: This is informatory message printed during autoconfiguration
                     52: indicating the type of hardware present the port configuration.
                     53: .PP
                     54: \fBvx%d: no buffers\fP.
                     55: All the command buffers were in use; this indicates the device
                     56: is constipated for some reason.
                     57: .PP
                     58: \fBvx%d: setq overflow\fP.
                     59: An attempt to append a command to an existing command buffer
                     60: failed because the buffer was full or the hardware doesn't
                     61: support this facility.
                     62: .PP
                     63: \fBvx%d: cmd q overflow\fP.
                     64: An attempt to place a new command on the command queue failed
                     65: because it was full.  The device is either overloaded or hung
                     66: up for some reason.  If this happens, the system tries to
                     67: reset the device to unwedge it.
                     68: .PP
                     69: \fBvx%d INTR ERR type %x v_dcd %x\fP.
                     70: An error was returned by the device in response to some command.
                     71: The command identifier and data carrier detect mask are printed
                     72: followed by the contents of the command buffer in error.
                     73: .PP
                     74: \fBvx%d: vcmdrsp interrupt\fP.
                     75: A command response interrupt was received from a bop (bit oriented
                     76: protocol) vioc.  This should not happen.
                     77: .PP
                     78: \fBvx%d: cmdresp debug\fP.
                     79: .PP
                     80: \fBvx%d: vunsol from BOP\fP.
                     81: An unsolicited interrupt was received from a bop vioc.  This should
                     82: not happen.
                     83: .PP
                     84: \fBvx%d: interrupt q overflow\fP.
                     85: The queue of pending interrupts to be delivered to the vioc is
                     86: full.  This is probably due to the vioc being wedged.  The system
                     87: resets the vioc if this occurs.
                     88: .PP
                     89: \fBvx%d: reset...\fP.
                     90: The system attempted to reset the vioc.
                     91: .SH BUGS

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.