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