1.\" $NetBSD: dmz.4,v 1.14 2017/08/01 11:11:17 wiz Exp $ 2.\" 3.\" Copyright (c) 1983, 1991, 1993 4.\" The Regents of the University of California. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. Neither the name of the University nor the names of its contributors 15.\" may be used to endorse or promote products derived from this software 16.\" without specific prior written permission. 17.\" 18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 21.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 28.\" SUCH DAMAGE. 29.\" 30.\" from: @(#)dmz.4 8.1 (Berkeley) 6/5/93 31.\" 32.Dd June 5, 1993 33.Dt DMZ 4 vax 34.Os 35.Sh NAME 36.Nm dmz 37.Nd 38.Tn DMZ-32 39serial terminal multiplexor 40.Sh SYNOPSIS 41.Cd "dmz0 at uba? csr 0160540" "vector dmzrinta dmzxinta dmzrintb dmzxintb dmzrintc dmzxintc" 42.Sh DESCRIPTION 43NOTE: This driver has not been ported from 44.Bx 4.4 45yet. 46.Pp 47The 48.Nm dmz 49device provides 24 lines of asynchronous serial line support. 50Modem control on all ports is available 51as an option for the H3014 distribution panel. 52.Pp 53An optional argument 54.Ar flags 55may be supplied with the device specification for 56.Nm dmz 57in the config file indicating 58that the line corresponding to 59bit number 60.Ar i 61is not properly 62connected, and should be treated as hard-wired with carrier 63always present. 64Thus specifying 65.Ql flags 0x000004 66for 67.Li dmz0 68would cause line 69.Pa ttya2 70to be treated in this way. 71.Pp 72Normal 73.Tn I/O 74control parameters for individual lines are managed by 75.Xr ioctl 2 76calls. 77Line speeds (there are 16 choices for the 78.Tn DMZ ) 79may be initiated via 80.Xr getty 8 81and 82.Xr stty 1 83or may be communicated by other programs which 84use 85.Xr ioctl 2 86such as 87.Xr ifconfig 8 , 88see 89.Xr tty 4 . 90.Pp 91The 92.Nm dmz 93driver normally enables the input silos with a short timeout 94(30 milliseconds); this allows multiple characters to be received 95per interrupt during periods of high-speed input. 96.Sh FILES 97.Bl -tag -width /dev/tty[abcefg][0-9a-n] -compact 98.It Pa /dev/tty[abcefg][0-9a-n] 99.El 100.Sh DIAGNOSTICS 101.Bl -diag 102.It dmz%d: NXM line %d. 103No response from the 104.Tn UNIBUS 105on a 106.Tn DMA 107transfer 108within a timeout period. 109This is often followed by a 110.Tn UNIBUS 111adapter 112error. 113This occurs most frequently when the 114.Tn UNIBUS 115is heavily loaded 116and when devices which hog the bus (such as 117.Tn RK07 Ns s ) 118are present. 119It is not serious. 120.It dmz%d: silo overflow. 121The character input silo overflowed 122before it could be serviced. 123This can happen if a hard error occurs when the 124.Tn CPU 125is running with elevated priority, as the system will 126then print a message on the console with interrupts disabled. 127It is not serious. 128.El 129.Sh SEE ALSO 130.Xr tty 4 131.Sh HISTORY 132The 133.Nm 134driver appeared in 135.Bx 4.3 . 136.Sh BUGS 137It should be possible to set the silo timeout with a configuration file option, 138as the value is a trade-off between efficiency and response time for flow 139control and character echo. 140