|
|
1.1 root 1: .\" Copyright (c) 1983 Regents of the University of California.
2: .\" All rights reserved. The Berkeley software License Agreement
3: .\" specifies the terms and conditions for redistribution.
4: .\"
5: .\" @(#)dmz.4 6.3 (Berkeley) 5/16/86
6: .\"
7: .TH DMZ 4 "April 7, 1986"
8: .UC 5
9: .SH NAME
10: dmz \- DMZ-32 terminal multiplexor
11: .SH SYNOPSIS
12: .B "device dmz0 at uba? csr 0160540"
13: .br
14: .ti +0.5i
15: .B "vector dmzrinta dmzxinta dmzrintb dmzxintb dmzrintc dmzxintc"
16: .SH DESCRIPTION
17: The
18: .I dmz
19: device provides 24 lines of asynchronous serial line support.
20: Modem control on all ports is available
21: as an option for the H3014 distribution panel.
22: .PP
23: Each line attached to a DMZ-32 serial line port behaves as described
24: in
25: .IR tty (4).
26: Input and output for each line may independently be set to run at any
27: of 16 speeds; see
28: .IR tty (4)
29: for the encoding.
30: .PP
31: Bit
32: .I i
33: of flags may be specified for a
34: .I dmz
35: to to say that a line is not properly connected, and that the
36: line should be treated as hard-wired with carrier always present.
37: Thus specifying ``flags 0x000004'' in the specification of
38: .IR dmz 0
39: would cause line
40: .I ttya2
41: to be treated in this way.
42: .PP
43: The
44: .I dmz
45: driver normally enables the input silos with a short timeout
46: (30 milliseconds); this allows multiple characters to be received
47: per interrupt during periods of high-speed input.
48: .SH FILES
49: /dev/tty[abcefg][0-9a-n]
50: .SH SEE ALSO
51: tty(4)
52: .SH DIAGNOSTICS
53: .BR "dmz%d: NXM line %d" .
54: No response from the UNIBUS on a DMA transfer
55: within a timeout period. This is often followed by a UNIBUS adapter
56: error. This occurs most frequently when the UNIBUS is heavily loaded
57: and when devices which hog the bus (such as RK07s) are present.
58: It is not serious.
59: .PP
60: .BR "dmz%d: silo overflow" .
61: The character input silo overflowed
62: before it could be serviced. This can happen if a hard error occurs
63: when the CPU is running with elevated priority, as the system will
64: then print a message on the console with interrupts disabled.
65: It is not serious.
66: .SH BUGS
67: It should be possible to set the silo timeout with a configuration file option,
68: as the value is a trade-off between efficiency and response time for flow
69: control and character echo.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.