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