.\" Copyright (c) 1983 Regents of the University of California.
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\" @(#)dmz.4 6.3 (Berkeley) 5/16/86
.TH DMZ 4 "April 7, 1986"
dmz \- DMZ-32 terminal multiplexor
.B "device dmz0 at uba? csr 0160540"
.B "vector dmzrinta dmzxinta dmzrintb dmzxintb dmzrintc dmzxintc"
device provides 24 lines of asynchronous serial line support.
Modem control on all ports is available
as an option for the H3014 distribution panel.
Each line attached to a DMZ-32 serial line port behaves as described
Input and output for each line may independently be set to run at any
of flags may be specified for a
to to say that a line is not properly connected, and that the
line should be treated as hard-wired with carrier always present.
Thus specifying ``flags 0x000004'' in the specification of
to be treated in this way.
driver normally enables the input silos with a short timeout
(30 milliseconds); this allows multiple characters to be received
per interrupt during periods of high-speed input.
.BR "dmz%d: NXM line %d" .
No response from the UNIBUS on a DMA transfer
within a timeout period. This is often followed by a UNIBUS adapter
error. This occurs most frequently when the UNIBUS is heavily loaded
and when devices which hog the bus (such as RK07s) are present.
.BR "dmz%d: silo overflow" .
The character input silo overflowed
before it could be serviced. This can happen if a hard error occurs
when the CPU is running with elevated priority, as the system will
then print a message on the console with interrupts disabled.
It should be possible to set the silo timeout with a configuration file option,
as the value is a trade-off between efficiency and response time for flow
control and character echo.