1.\" $NetBSD: dl.4,v 1.1 1997/02/04 19:16:10 ragge Exp $ 2.\" 3.\" Copyright (c) 1997 Ben Harris. All rights reserved. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" 1. Redistributions of source code must retain the above copyright 9.\" notice, this list of conditions and the following disclaimer. 10.\" 2. Redistributions in binary form must reproduce the above copyright 11.\" notice, this list of conditions and the following disclaimer in the 12.\" documentation and/or other materials provided with the distribution. 13.\" 3. All advertising materials mentioning features or use of this software 14.\" must display the following acknowledgement: 15.\" This product includes software developed by Ben Harris. 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.Dd January 28, 1997 32.Os NetBSD 1.2 33.Dt DL 4 vax 34.Sh NAME 35.Nm dl 36.Nd 37.Tn DL11 Ns / Ns Tn DLV11 38serial device driver 39.Sh SYNOPSIS 40.Cd "dl0 at uba? csr 0176500" 41.Cd "dl1 at uba? csr 0176510" 42.Cd "dl2 at uba? csr 0176520" 43.Cd "dl3 at uba? csr 0176530" 44.Sh DESCRIPTION 45The 46.Nm 47driver controls a 48.Tn DL11 Ns -compatible 49asynchronous serial card, and probably things compatible with it. A 50four-port 51.Tn DLV11-J 52will appear four times in the device list, as the ports look like 53separate cards to the driver. 54.Pp 55.Pp 56The 57.Nm 58driver provides the normal interface described in 59.Xr tty 4 , 60but many of the configuration calls are unsupported, since their 61functions are handled by jumpers or switches on the serial card 62itself. Calls related to modem-control lines are also ignored, since 63these cards lack them. 64.Pp 65There's a chance this driver might also work with an 66.Tn LP11 , 67an 68.Tn LPV11 69or even a 70.Tn PC11 , 71but it hasn't been tested. 72.Sh FILES 73.Bl -tag -width /dev/ttyJ? -compact 74.It Pa /dev/ttyJ? 75Special files for communicating with dl devices. 76.\" .Sh EXAMPLES 77.Sh DIAGNOSTICS 78.Bl -diag 79.It dl%d: rx overrun. 80The character in the recieve buffer wasn't read before the next 81character arrived, and has been lost. 82.It dl%d: stray rx interrupt. 83The driver was called to service a receive interrupt, but there was 84nothing for it to read. 85.Sh SEE ALSO 86.Xr tty 4 87.\" .Sh STANDARDS 88.Sh HISTORY 89The 90.Nm 91driver was written for 92.Tn NetBSD 931.2B. 94.Sh AUTHOR 95Ben Harris <bjh@mail.dotcom.fr> 96.Sh BUGS 97The 98.Tn DL11 99and friends only have single-character receive and transmit buffers, 100so an interrupt is generated for every character received or 101transmitted. Attempting to receive data at even moderately high rates 102will cause rx overruns. Fast transmission seems to be fine though. 103.Pp 104There is no support in the driver for the paper-tape reader on an 105.Tn LT33 106attached via a 107.Tn DLV11-KA 108or similar. 109.Pp 110The overrun message is logged in the interrupt routine itself, which 111will probably just make the problem worse. 112.Pp 113The CSR printed on startup is that of the receiver, while the 114interrupt vector is that of the transmitter. 115.Pp 116In order to determine the card's interrupt vector, the driver sends a 117.Dv NUL 118to each port. This may confuse things attached to them. 119.Pp 120The driver has so far only been tested on a 121.Tn DLV11-J . 122It may or may not work on the other cards it claims to support. 123