BSD 4_4 release

[unix-history] / usr / src / share / man / man4 / man4.vax / dmz.4

diff --git a/usr/src/share/man/man4/man4.vax/dmz.4 b/usr/src/share/man/man4/man4.vax/dmz.4
index be8d2f5..4fd8fd2 100644 (file)
--- a/usr/src/share/man/man4/man4.vax/dmz.4
+++ b/usr/src/share/man/man4/man4.vax/dmz.4
@@ -1,70 +1,135 @@
-.\" Copyright (c) 1983 Regents of the University of California.
-.\" All rights reserved.  The Berkeley software License Agreement
-.\" specifies the terms and conditions for redistribution.
+.\" Copyright (c) 1983, 1991, 1993
+.\"    The Regents of the University of California.  All rights reserved.

 .\"
 .\"

-.\"    @(#)dmz.4       6.1 (Berkeley) %G%
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"    This product includes software developed by the University of
+.\"    California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.

 .\"
 .\"

-.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
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)dmz.4      8.1 (Berkeley) 6/5/93
+.\"
+.Dd June 5, 1993
+.Dt DMZ 4 vax
+.Os BSD 4.2
+.Sh NAME
+.Nm dmz
+.Nd
+.Tn DMZ-32
+terminal multiplexor
+.Sh SYNOPSIS
+.Cd "device dmz0 at uba? csr 0160540" "vector dmzrinta dmzxinta dmzrintb dmzxintb dmzrintc dmzxintc"
+.Sh DESCRIPTION

 The 
 The 

-.I dmz
+.Nm dmz

 device provides 24 lines of asynchronous serial line support.
 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.
 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
+.Pp
+An optional argument
+.Ar flags
+may be supplied with the device specification for
+.Nm dmz
+in the config file indicating
+that the line corresponding to
+bit number
+.Ar i
+is not properly
+connected, and should be treated as hard-wired with carrier
+always present.  Thus specifying
+.Ql flags 0x000004
+for
+.Li dmz0

 would cause line
 would cause line

-.I ttya2
+.Pa ttya2

 to be treated in this way.
 to be treated in this way.

-.PP
+.Pp
+Normal
+.Tn I/O
+control parameters for individual lines are managed by
+.Xr ioctl 2
+calls.
+Line speeds (there are 16 choices for the
+.Tn DMZ )
+may be initiated via
+.Xr getty 8
+and
+.Xr stty 1
+or may be communicated by other programs which
+utilize
+.Xr ioctl
+such as
+.Xr ifcongif 8 ,
+see
+.Xr tty 4  .
+.Pp

 The
 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.
+.Nm dmz
+driver normally enables the input silos with a short timeout
+(30 milliseconds); this allows multiple characters to be received
+per interrupt during periods of high-speed input.
+.Sh FILES
+.Bl -tag -width /dev/tty[abcefg][0-9a-n] -compact
+.It Pa /dev/tty[abcefg][0-9a-n]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dmz%d: NXM line %d.
+No response from the
+.Tn UNIBUS
+on a
+.Tn DMA
+transfer
+within a timeout period.  This is often followed by a
+.Tn UNIBUS
+adapter
+error.  This occurs most frequently when the
+.Tn UNIBUS
+is heavily loaded
+and when devices which hog the bus (such as
+.Tn RK07 Ns s )
+are present.

 It is not serious.
 It is not serious.

-.PP
-.BR "dmz%d: silo overflow" .
+.Pp
+.It dmz%d: silo overflow.

 The character input silo overflowed
 before it could be serviced.  This can happen if a hard error occurs
 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
+when the
+.Tn CPU
+is running with elevated priority, as the system will

 then print a message on the console with interrupts disabled.
 It is not serious.
 then print a message on the console with interrupts disabled.
 It is not serious.

+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .
+.Sh BUGS
+It should be possible to set the silo timeout with a configuration file option,
+as the value is a trade-off between efficiency and response time for flow
+control and character echo.