Return to uu.4 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man4 / vax

Annotation of 43BSDTahoe/man/man4/vax/uu.4, revision 1.1.1.1

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

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.