xref: /netbsd-src/share/man/man4/man4.vax/uu.4 (revision 3b01aba77a7a698587faaae455bbfe740923c1f5)
1.\"	$NetBSD: uu.4,v 1.7 2001/04/11 19:23:02 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: @(#)uu.4	8.1 (Berkeley) 6/5/93
35.\"
36.Dd June 5, 1993
37.Dt UU 4 vax
38.Os
39.Sh NAME
40.Nm uu
41.Nd
42.Tn TU58 Ns / Tn DECtape II UNIBUS
43cassette interface
44.Sh SYNOPSIS
45.Cd "options UUDMA"
46.Cd "uu0 at uba0 csr 0176500 vector uurintr uuxintr"
47.Sh DESCRIPTION
48The
49.Nm uu
50device provides access to dual
51.Tn DEC
52.Tn TU58
53tape cartridge drives
54connected to the
55.Tn UNIBUS
56via a
57.Tn DL11-W
58interface module.
59.Pp
60The interface supports only block
61.Tn I/O
62to the
63.Tn TU58
64cassettes (see
65.Xr physio 4 ) .
66The drives are normally manipulated with the
67.Xr arff 8
68program using the ``m'' and ``f'' options.
69.Pp
70The driver provides for an optional write and verify
71(read after write) mode that is activated by specifying the
72``a'' device.
73.Pp
74The
75.Tn TU58
76is treated as a single device by the system even
77though it has two separate drives,
78.Sq Li uu0
79and
80.Sq Li uu1 .
81If there is
82more than one
83.Tn TU58
84unit on a system, the extra drives
85are named
86.Sq Li uu2 ,
87.Sq Li uu3
88etc.
89.Sh NOTES
90Assembly language code to assist the driver in handling
91the receipt of data (using a pseudo-dma approach) should
92be included when using this driver; specify
93.Sq Li options UUDMA
94in the configuration file.
95.Sh FILES
96.Bl -tag -width /dev/uu?a -compact
97.It Pa /dev/uu?
98.It Pa /dev/uu?a
99.El
100.Sh DIAGNOSTICS
101.Bl -diag
102.It uu%d: no bp, active %d.
103A transmission complete interrupt was received with no outstanding
104.Tn I/O
105request. This indicates a hardware problem.
106.Pp
107.It uu%d protocol error, state=%s, op=%x, cnt=%d, block=%d.
108The driver entered an illegal state.  The information printed
109indicates the illegal state, the
110operation currently being executed,
111the
112.Tn I/O
113count, and the block number on the cassette.
114.Pp
115.It uu%d: break received, transfer restarted.
116The
117.Tn TU58
118was sending a continuous break signal and had
119to be reset. This may indicate a hardware problem, but
120the driver will attempt to recover from the error.
121.Pp
122.It uu%d receive state error, state=%s, byte=%x.
123The driver entered an illegal state in the receiver finite
124state machine.  The state is shown along with the control
125byte of the received packet.
126.Pp
127.It uu%d: read stalled.
128A timer watching the controller detected no interrupt for
129an extended period while an operation was outstanding.
130This usually indicates that one or more receiver interrupts
131were lost and the transfer is restarted.
132.Pp
133.It uu%d: hard error bn%d, pk_mod %o.
134The device returned a status code indicating a hard error. The
135actual error code is shown in octal. No retries are attempted
136by the driver.
137.El
138.Sh ERRORS
139The following errors may be returned:
140.Bl -tag -width [ENXIO]
141.It Bq Er ENXIO
142Nonexistent drive (on open);
143offset is too large or bad (undefined)
144.Xr ioctl 2
145code.
146.It Bq Er EIO
147Open failed, the device could not be reset.
148.It Bq Er EBUSY
149Drive in use.
150.El
151.Sh SEE ALSO
152.Xr tu 4 ,
153.Xr arff 8
154.Sh HISTORY
155The
156.Nm
157driver appeared in
158.Bx 4.2 .
159