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