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