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