1.\" $NetBSD: dmf.4,v 1.10 2003/08/07 10:31:10 agc Exp $ 2.\" 3.\" Copyright (c) 1983, 1991, 1993 4.\" The Regents of the University of California. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. Neither the name of the University nor the names of its contributors 15.\" may be used to endorse or promote products derived from this software 16.\" without specific prior written permission. 17.\" 18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 21.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 28.\" SUCH DAMAGE. 29.\" 30.\" from: @(#)dmf.4 8.1 (Berkeley) 6/5/93 31.\" 32.Dd June 5, 1993 33.Dt DMF 4 vax 34.Os 35.Sh NAME 36.Nm dmf 37.Nd 38.Tn DMF-32 39serial terminal multiplexor 40.Sh SYNOPSIS 41.Cd "dmf0 at uba? csr 0160340 vector dmfsrint dmfsxint dmfdaint dmfdbint dmfrint dmfxint dmflint" 42.Sh DESCRIPTION 43NOTE: This driver has not been ported from 44.Bx 4.4 45yet. 46.Pp 47The 48.Nm dmf 49device provides 8 lines of asynchronous serial line support. 50The first two of these have full modem control. 51The device also provides a line printer port 52similar to the 53.Tn LP-11 . 54Other features of the 55.Tn DMF-32 56are not supported. 57During autoconfiguration, the driver examines the configuration of each 58.Tn DMF-32 59and adjusts the interrupt vectors so that fewer vector locations are used 60if possible. 61.Pp 62An optional argument 63.Ar flags 64may be supplied with the device specification 65in the config file indicating 66that the line corresponding to 67bit number 68.Ar i 69is not properly 70connected, and should be treated as hard-wired with carrier 71always present. Thus specifying 72.Ql flags 0x04 73for 74.Li dmf0 75would cause line 76.Pa ttyA2 77to be treated in this way. 78Flags should be set for all lines without hardware support for modem control. 79.Pp 80Normal 81.Tn I/O 82control parameters for individual lines are managed by 83.Xr ioctl 2 84calls. 85Line speeds may be initiated via 86.Xr getty 8 87and 88.Xr stty 1 89or may be communicated by other programs which 90use 91.Xr ioctl 2 92such as 93.Xr ifconfig 8 , 94see 95.Xr tty 4 . 96.Pp 97The serial line part of the 98.Nm dmf 99driver normally enables the input silos with a short timeout 100(30 milliseconds); this allows multiple characters to be received 101per interrupt during periods of high-speed input. 102.Pp 103A line printer port on a 104.Nm dmf 105is designated by 106a minor device number of the form 107.Pf 128+ Ns Ar n . 108See 109.Xr MAKEDEV 8 . 110Column and lines per page may be changed from the default 111132 columns and 66 lines by encoding the number of columns 112in bits 8-15 of flags and the number of lines in bits 16-23. 113This device does not provide the fancy output canonicalization 114features of the 115.Xr lp 4 116driver. 117.Sh FILES 118.Bl -tag -width "/dev/tty[A-CE-I][0-7]" -compact 119.It Pa /dev/tty[A-CE-I][0-7] 120.It Pa /dev/ttyd[0-7] 121.It Pa /dev/lp 122.El 123.Sh DIAGNOSTICS 124.Bl -diag 125.It dmf%d: NXM line %d. 126No response from 127.Tn UNIBUS 128on a DMA transfer 129within a timeout period. This is often followed by a 130.Tn UNIBUS 131adapter 132error. This occurs most frequently when the 133.Tn UNIBUS 134is heavily loaded 135and when devices which hog the bus (such as 136.Tn RK07 Ns s ) 137are present. 138It is not serious. 139.Pp 140.It dmf%d: silo overflow. 141The character input silo overflowed 142before it could be serviced. This can happen if a hard error occurs 143when the 144.Tn CPU 145is running with elevated priority, as the system will 146then print a message on the console with interrupts disabled. 147It is not serious. 148.Pp 149.It dmfsrint, dmfsxint, dmfdaint, dmfdbint. 150One of the unsupported parts of the dmf interrupted; something 151is amiss, check your interrupt vectors for a conflict with another 152device. 153.El 154.Sh SEE ALSO 155.Xr tty 4 156.Sh HISTORY 157The 158.Nm 159driver appeared in 160.Bx 4.2 . 161.Sh BUGS 162It should be possible to set the silo timeout with a configuration file option, 163as the value is a trade-off between efficiency and response time for flow 164control and character echo. 165