xref: /netbsd/share/man/man4/man4.vax/dl.4 (revision bf9ec67e)
1.\"	$NetBSD: dl.4,v 1.9 2002/02/13 08:18:06 ross 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. The name of the author may not be used to endorse or promote products
14.\"    derived from this software without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
17.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
18.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
19.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
20.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
21.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
22.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
23.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
24.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
25.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
26.Dd January 28, 1997
27.Os
28.Dt DL 4 vax
29.Sh NAME
30.Nm dl
31.Nd
32.Tn DL11 Ns / Ns Tn DLV11
33serial device driver
34.Sh SYNOPSIS
35.Cd "dl0 at uba? csr 0176500"
36.Cd "dl1 at uba? csr 0176510"
37.Cd "dl2 at uba? csr 0176520"
38.Cd "dl3 at uba? csr 0176530"
39.Sh DESCRIPTION
40The
41.Nm
42driver controls a
43.Tn DL11 Ns -compatible
44asynchronous serial card, and probably things compatible with it.  A
45four-port
46.Tn DLV11-J
47will appear four times in the device list, as the ports look like
48separate cards to the driver.
49.Pp
50.Pp
51The
52.Nm
53driver provides the normal interface described in
54.Xr tty 4 ,
55but many of the configuration calls are unsupported, since their
56functions are handled by jumpers or switches on the serial card
57itself.  Calls related to modem-control lines are also ignored, since
58these cards lack them.
59.Pp
60There's a chance this driver might also work with an
61.Tn LP11 ,
62an
63.Tn LPV11
64or even a
65.Tn PC11 ,
66but it hasn't been tested.
67.Sh FILES
68.Bl -tag -width /dev/ttyJ? -compact
69.It Pa /dev/ttyJ?
70Special files for communicating with dl devices.
71.El
72.\" .Sh EXAMPLES
73.Sh DIAGNOSTICS
74.Bl -diag
75.It dl%d: rx overrun.
76The character in the receive buffer wasn't read before the next
77character arrived, and has been lost.
78.It dl%d: stray rx interrupt.
79The driver was called to service a receive interrupt, but there was
80nothing for it to read.
81.El
82.Sh SEE ALSO
83.Xr tty 4
84.\" .Sh STANDARDS
85.Sh HISTORY
86The
87.Nm
88driver was written for
89.Nx 1.3 .
90.Sh AUTHORS
91Ben Harris \*[Lt]bjh21@netbsd.org\*[Gt]
92.Sh BUGS
93The
94.Tn DL11
95and friends only have single-character receive and transmit buffers,
96so an interrupt is generated for every character received or
97transmitted.  Attempting to receive data at even moderately high rates
98will cause rx overruns.  Fast transmission seems to be fine though.
99.Pp
100There is no support in the driver for the paper-tape reader on an
101.Tn LT33
102attached via a
103.Tn DLV11-KA
104or similar.
105.Pp
106The overrun message is logged in the interrupt routine itself, which
107will probably just make the problem worse.
108.Pp
109The CSR printed on startup is that of the receiver, while the
110interrupt vector is that of the transmitter.
111.Pp
112In order to determine the card's interrupt vector, the driver sends a
113.Dv NUL
114to each port.  This may confuse things attached to them.
115.Pp
116The driver has so far only been tested on a
117.Tn DLV11-J .
118It may or may not work on the other cards it claims to support.
119