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