1.\" Copyright (c) 1983, 1991 Regents of the University of California. 2.\" 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.\" from: @(#)dmz.4 6.4 (Berkeley) 3/27/91 33.\" $Id: dmz.4,v 1.2 1993/08/01 07:36:26 mycroft Exp $ 34.\" 35.Dd March 27, 1991 36.Dt DMZ 4 vax 37.Os BSD 4.2 38.Sh NAME 39.Nm dmz 40.Nd 41.Tn DMZ-32 42terminal multiplexor 43.Sh SYNOPSIS 44.Cd "device dmz0 at uba? csr 0160540" "vector dmzrinta dmzxinta dmzrintb dmzxintb dmzrintc dmzxintc" 45.Sh DESCRIPTION 46The 47.Nm dmz 48device provides 24 lines of asynchronous serial line support. 49Modem control on all ports is available 50as an option for the H3014 distribution panel. 51.Pp 52An optional argument 53.Ar flags 54may be supplied with the device specification for 55.Nm dmz 56in the config file indicating 57that the line corresponding to 58bit number 59.Ar i 60is not properly 61connected, and should be treated as hard-wired with carrier 62always present. Thus specifying 63.Ql flags 0x000004 64for 65.Li dmz0 66would cause line 67.Pa ttya2 68to be treated in this way. 69.Pp 70Normal 71.Tn I/O 72control parameters for individual lines are managed by 73.Xr ioctl 2 74calls. 75Line speeds (there are 16 choices for the 76.Tn DMZ ) 77may be initiated via 78.Xr getty 8 79and 80.Xr stty 1 81or may be communicated by other programs which 82utilize 83.Xr ioctl 84such as 85.Xr ifcongif 8 , 86see 87.Xr tty 4 . 88.Pp 89The 90.Nm dmz 91driver normally enables the input silos with a short timeout 92(30 milliseconds); this allows multiple characters to be received 93per interrupt during periods of high-speed input. 94.Sh FILES 95.Bl -tag -width /dev/tty[abcefg][0-9a-n] -compact 96.It Pa /dev/tty[abcefg][0-9a-n] 97.El 98.Sh DIAGNOSTICS 99.Bl -diag 100.It dmz%d: NXM line %d. 101No response from the 102.Tn UNIBUS 103on a 104.Tn DMA 105transfer 106within a timeout period. This is often followed by a 107.Tn UNIBUS 108adapter 109error. This occurs most frequently when the 110.Tn UNIBUS 111is heavily loaded 112and when devices which hog the bus (such as 113.Tn RK07 Ns s ) 114are present. 115It is not serious. 116.Pp 117.It dmz%d: silo overflow. 118The character input silo overflowed 119before it could be serviced. This can happen if a hard error occurs 120when the 121.Tn CPU 122is running with elevated priority, as the system will 123then print a message on the console with interrupts disabled. 124It is not serious. 125.El 126.Sh SEE ALSO 127.Xr tty 4 128.Sh HISTORY 129The 130.Nm 131driver appeared in 132.Bx 4.3 . 133.Sh BUGS 134It should be possible to set the silo timeout with a configuration file option, 135as the value is a trade-off between efficiency and response time for flow 136control and character echo. 137