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