xref: /netbsd-src/share/man/man4/man4.vax/dmf.4 (revision cda4f8f6ee55684e8d311b86c99ea59191e6b74f)
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.\"     @(#)dmf.4	8.1 (Berkeley) 6/5/93
33.\"
34.Dd June 5, 1993
35.Dt DMF 4 vax
36.Os BSD 4.2
37.Sh NAME
38.Nm dmf
39.Nd
40.Tn DMF-32
41terminal multiplexor
42.Sh SYNOPSIS
43.Cd "device dmf0 at uba? csr 0160340 vector dmfsrint dmfsxint dmfdaint dmfdbint dmfrint dmfxint dmflint"
44.Sh DESCRIPTION
45The
46.Nm dmf
47device provides 8 lines of asynchronous serial line support.
48The first two of these have full modem control.
49The device also provides a line printer port
50similar to the
51.Tn LP-11 .
52Other features of the
53.Tn DMF-32
54are not supported.
55During autoconfiguration, the driver examines the configuration of each
56.Tn DMF-32
57and adjusts the interrupt vectors so that fewer vector locations are used
58if possible.
59.Pp
60An optional argument
61.Ar flags
62may be supplied with the device specification
63in the config file indicating
64that the line corresponding to
65bit number
66.Ar i
67is not properly
68connected, and should be treated as hard-wired with carrier
69always present.  Thus specifying
70.Ql flags 0x04
71for
72.Li dmf0
73would cause line
74.Pa ttyA2
75to be treated in this way.
76Flags should be set for all lines without hardware support for modem control.
77.Pp
78Normal
79.Tn I/O
80control parameters for individual lines are managed by
81.Xr ioctl 2
82calls.
83Line speeds may be initiated via
84.Xr getty 8
85and
86.Xr stty 1
87or may be communicated by other programs which
88utilize
89.Xr ioctl
90such as
91.Xr ifcongif 8 ,
92see
93.Xr tty 4  .
94.Pp
95The serial line part of the
96.Nm dmf
97driver normally enables the input silos with a short timeout
98(30 milliseconds); this allows multiple characters to be received
99per interrupt during periods of high-speed input.
100.Pp
101A line printer port on a
102.Nm dmf
103is designated by
104a minor device number of the form
105.Pf 128+ Ns Ar n .
106See
107.Xr MAKEDEV 8 .
108Column and lines per page may be changed from the default
109132 columns and 66 lines by encoding the number of columns
110in bits 8-15 of flags and the number of lines in bits 16-23.
111This device does not provide the fancy output canonicalization
112features of the
113.Xr lp 4
114driver.
115.Sh FILES
116.Bl -tag -width "/dev/tty[A-CE-I][0-7]" -compact
117.It Pa /dev/tty[A-CE-I][0-7]
118.It Pa /dev/ttyd[0-7]
119.It Pa /dev/lp
120.El
121.Sh DIAGNOSTICS
122.Bl -diag
123.It dmf%d: NXM line %d.
124No response from
125.Tn UNIBUS
126on a DMA transfer
127within a timeout period.  This is often followed by a
128.Tn UNIBUS
129adapter
130error.  This occurs most frequently when the
131.Tn UNIBUS
132is heavily loaded
133and when devices which hog the bus (such as
134.Tn RK07 Ns s )
135are present.
136It is not serious.
137.Pp
138.It dmf%d: silo overflow.
139The character input silo overflowed
140before it could be serviced.  This can happen if a hard error occurs
141when the
142.Tn CPU
143is running with elevated priority, as the system will
144then print a message on the console with interrupts disabled.
145It is not serious.
146.Pp
147.It dmfsrint, dmfsxint, dmfdaint, dmfdbint.
148One of the unsupported parts of the dmf interrupted; something
149is amiss, check your interrupt vectors for a conflict with another
150device.
151.El
152.Sh SEE ALSO
153.Xr tty 4
154.Sh HISTORY
155The
156.Nm
157driver appeared in
158.Bx 4.2 .
159.Sh BUGS
160It should be possible to set the silo timeout with a configuration file option,
161as the value is a trade-off between efficiency and response time for flow
162control and character echo.
163