date and time created 86/04/08 14:44:18 by donn

SCCS-vsn: share/man/man4/man4.vax/dmz.4 6.1

diff --git a/usr/src/share/man/man4/man4.vax/dmz.4 b/usr/src/share/man/man4/man4.vax/dmz.4
new file mode 100644 (file)
index 0000000..be8d2f5
--- /dev/null
+++ b/usr/src/share/man/man4/man4.vax/dmz.4
@@ -0,0 +1,70 @@
+.\" Copyright (c) 1983 Regents of the University of California.
+.\" All rights reserved.  The Berkeley software License Agreement
+.\" specifies the terms and conditions for redistribution.
+.\"
+.\"    @(#)dmz.4       6.1 (Berkeley) %G%
+.\"
+.TH DMZ 4 "April 7, 1986"
+.UC 5
+.SH NAME
+dmz \- DMZ-32 terminal multiplexor
+.SH SYNOPSIS
+.B "device dmz0 at uba? csr 0160540"
+.br
+.ti +0.5i
+.B "vector dmzrinta dmzxinta dmzrintb dmzxintb dmzrintc dmzxintc"
+.SH DESCRIPTION
+The 
+.I dmz
+device provides 24 lines of asynchronous serial line support.
+The DMZ-32 is connected to an H3014 distribution panel
+by a cable that may be up to a mile in length and
+the two ends communicate using a T1 protocol.
+Modem control on all ports is available
+as an option for the H3014 distribution panel.
+.PP
+Each line attached to a DMZ-32 serial line port behaves as described
+in
+.IR tty (4).
+Input and output for each line may independently be set to run at any
+of 16 speeds; see
+.IR tty (4)
+for the encoding.
+.PP
+Bit
+.I i
+of flags may be specified for a
+.I dmz
+to to say that a line is not properly connected, and that the
+line should be treated as hard-wired with carrier always present.
+Thus specifying ``flags 0x000004'' in the specification of 
+.IR dmz 0
+would cause line
+.I ttya2
+to be treated in this way.
+.PP
+The
+.I dmz
+driver normally uses input silos and polls for input at each clock
+tick (10 milliseconds).
+It uses an adaptive algorithm on output
+to decide whether to use programmed I/O or DMA
+based on the amount of data to send.
+.SH FILES
+/dev/tty[abc][0-9a-n]
+.SH SEE ALSO
+tty(4)
+.SH DIAGNOSTICS
+.BR "dmz%d: NXM line %d" .
+No response from the UNIBUS on a DMA transfer
+within a timeout period.  This is often followed by a UNIBUS adapter
+error.  This occurs most frequently when the UNIBUS is heavily loaded
+and when devices which hog the bus (such as RK07s) are present.
+It is not serious.
+.PP
+.BR "dmz%d: silo overflow" .
+The character input silo overflowed
+before it could be serviced.  This can happen if a hard error occurs
+when the CPU is running with elevated priority, as the system will
+then print a message on the console with interrupts disabled.
+It is not serious.