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