1.\" $NetBSD: dmz.4,v 1.4 1997/10/19 12:59:26 mrg 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 BSD 4.2 39.Sh NAME 40.Nm dmz 41.Nd 42.Tn DMZ-32 43terminal multiplexor 44.Sh SYNOPSIS 45.Cd "device dmz0 at uba? csr 0160540" "vector dmzrinta dmzxinta dmzrintb dmzxintb dmzrintc dmzxintc" 46.Sh DESCRIPTION 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. Thus specifying 64.Ql flags 0x000004 65for 66.Li dmz0 67would cause line 68.Pa ttya2 69to be treated in this way. 70.Pp 71Normal 72.Tn I/O 73control parameters for individual lines are managed by 74.Xr ioctl 2 75calls. 76Line speeds (there are 16 choices for the 77.Tn DMZ ) 78may be initiated via 79.Xr getty 8 80and 81.Xr stty 1 82or may be communicated by other programs which 83utilize 84.Xr ioctl 85such as 86.Xr ifcongif 8 , 87see 88.Xr tty 4 . 89.Pp 90The 91.Nm dmz 92driver normally enables the input silos with a short timeout 93(30 milliseconds); this allows multiple characters to be received 94per interrupt during periods of high-speed input. 95.Sh FILES 96.Bl -tag -width /dev/tty[abcefg][0-9a-n] -compact 97.It Pa /dev/tty[abcefg][0-9a-n] 98.El 99.Sh DIAGNOSTICS 100.Bl -diag 101.It dmz%d: NXM line %d. 102No response from the 103.Tn UNIBUS 104on a 105.Tn DMA 106transfer 107within a timeout period. This is often followed by a 108.Tn UNIBUS 109adapter 110error. This occurs most frequently when the 111.Tn UNIBUS 112is heavily loaded 113and when devices which hog the bus (such as 114.Tn RK07 Ns s ) 115are present. 116It is not serious. 117.Pp 118.It dmz%d: silo overflow. 119The character input silo overflowed 120before it could be serviced. This can happen if a hard error occurs 121when the 122.Tn CPU 123is running with elevated priority, as the system will 124then print a message on the console with interrupts disabled. 125It is not serious. 126.El 127.Sh SEE ALSO 128.Xr tty 4 129.Sh HISTORY 130The 131.Nm 132driver appeared in 133.Bx 4.3 . 134.Sh BUGS 135It should be possible to set the silo timeout with a configuration file option, 136as the value is a trade-off between efficiency and response time for flow 137control and character echo. 138