projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| f1528ab1 C |
1 | .TH UU 4 "27 July 1983" |
| 2 | .UC 4 | |
| 3 | .SH NAME | |
| 4 | uu \- TU58/DECtape II UNIBUS cassette interface | |
| 5 | .SH SYNOPSIS | |
| 6 | .B "options UUDMA" | |
| 7 | .br | |
| 8 | .B "device uu0 at uba0 csr 0176500 vector uurintr uuxintr" | |
| 9 | .SH DESCRIPTION | |
| 10 | The | |
| 11 | .I uu | |
| 12 | device provides access to dual DEC TU58 tape cartridge drives | |
| 13 | connected to the UNIBUS via a DL11-W interface module. | |
| 14 | .PP | |
| 15 | The interface supports only block i/o to the TU58 cassettes. | |
| 16 | The drives are normally manipulated with the | |
| 17 | .IR arff (8V) | |
| 18 | program using the ``m'' and ``f'' options. | |
| 19 | .PP | |
| 20 | The driver provides for an optional write and verify | |
| 21 | (read after write) mode that is activated by specifying the | |
| 22 | ``a'' device. | |
| 23 | .PP | |
| 24 | The TU58 is treated as a single device by the system even | |
| 25 | though it has two separate drives, ``uu0'' and ``uu1''. If there is | |
| 26 | more than one TU58 unit on a system, the extra drives | |
| 27 | are named ``uu2'', ``uu3'' etc. | |
| 28 | .SH NOTES | |
| 29 | Assembly language code to assist the driver in handling | |
| 30 | the receipt of data (using a pseudo-dma approach) should | |
| 31 | be included when using this driver; specify ``options UUDMA'' | |
| 32 | in the configuration file. | |
| 33 | .SH ERRORS | |
| 34 | The following errors may be returned: | |
| 35 | .TP 12 | |
| 36 | [ENXIO] | |
| 37 | Nonexistent drive (on open); | |
| 38 | offset is too large or bad (undefined) ioctl code. | |
| 39 | .TP | |
| 40 | [EIO] | |
| 41 | Open failed, the device could not be reset. | |
| 42 | .TP | |
| 43 | [EBUSY] | |
| 44 | Drive in use. | |
| 45 | .SH FILES | |
| 46 | /dev/uu? | |
| 47 | .br | |
| 48 | /dev/uu?a | |
| 49 | .SH SEE ALSO | |
| 50 | tu(4), arff(8V) | |
| 51 | .SH DIAGNOSTICS | |
| 52 | .BR "uu%d: no bp, active %d" . | |
| 53 | A transmission complete interrupt was received with no outstanding | |
| 54 | i/o request. This indicates a hardware problem. | |
| 55 | .PP | |
| 56 | .BR "uu%d protocol error, state=%s, op=%x, cnt=%d, block=%d" . | |
| 57 | The driver entered an illegal state. The information printed | |
| 58 | indicates the illegal state, the | |
| 59 | operation currently being executed, | |
| 60 | the i/o count, and the block number on the cassette. | |
| 61 | .PP | |
| 62 | .BR "uu%d: break received, transfer restarted" . | |
| 63 | The TU58 was sending a continuous break signal and had | |
| 64 | to be reset. This may indicate a hardware problem, but | |
| 65 | the driver will attempt to recover from the error. | |
| 66 | .PP | |
| 67 | .BR "uu%d receive state error, state=%s, byte=%x" . | |
| 68 | The driver entered an illegal state in the receiver finite | |
| 69 | state machine. The state is shown along with the control | |
| 70 | byte of the received packet. | |
| 71 | .PP | |
| 72 | .BR "uu%d: read stalled" . | |
| 73 | A timer watching the controller detected no interrupt for | |
| 74 | an extended period while an operation was outstanding. | |
| 75 | This usually indicates that one or more receiver interrupts | |
| 76 | were lost and the transfer is restarted. | |
| 77 | .PP | |
| 78 | .BR "uu%d: hard error bn%d, pk_mod %o" . | |
| 79 | The device returned a status code indicating a hard error. The | |
| 80 | actual error code is shown in octal. No retries are attempted | |
| 81 | by the driver. |