usr/share/man/cat4/vax/uu.0

UU(4)             BSD Programmer's Manual (VAX Architecture)             UU(4)

N\bNA\bAM\bME\bE
     u\buu\bu - TU58/ DECtape II UNIBUS cassette interface

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     o\bop\bpt\bti\bio\bon\bns\bs U\bUU\bUD\bDM\bMA\bA
     d\bde\bev\bvi\bic\bce\be u\buu\bu0\b0 a\bat\bt u\bub\bba\ba0\b0 c\bcs\bsr\br 0\b01\b17\b76\b65\b50\b00\b0 v\bve\bec\bct\bto\bor\br u\buu\bur\bri\bin\bnt\btr\br u\buu\bux\bxi\bin\bnt\btr\br

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     The u\buu\bu device provides access to dual DEC TU58 tape cartridge drives con-
     nected to the UNIBUS via a DL11-W interface module.

     The interface supports only block I/O to the TU58 cassettes (see
     physio(4)).  The drives are normally manipulated with the arff(8) program
     using the ``m'' and ``f'' options.

     The driver provides for an optional write and verify (read after write)
     mode that is activated by specifying the ``a'' device.

     The TU58 is treated as a single device by the system even though it has
     two separate drives, `uu0' and `uu1'. If there is more than one TU58 unit
     on a system, the extra drives are named `uu2', `uu3' etc.

N\bNO\bOT\bTE\bES\bS
     Assembly language code to assist the driver in handling the receipt of
     data (using a pseudo-dma approach) should be included when using this
     driver; specify `options UUDMA' in the configuration file.

F\bFI\bIL\bLE\bES\bS
     /dev/uu?
     /dev/uu?a

D\bDI\bIA\bAG\bGN\bNO\bOS\bST\bTI\bIC\bCS\bS
     u\buu\bu%\b%d\bd:\b: n\bno\bo b\bbp\bp,\b, a\bac\bct\bti\biv\bve\be %\b%d\bd.\b.  A transmission complete interrupt was received
     with no outstanding I/O request. This indicates a hardware problem.

     u\buu\bu%\b%d\bd p\bpr\bro\bot\bto\boc\bco\bol\bl e\ber\brr\bro\bor\br,\b, s\bst\bta\bat\bte\be=\b=%\b%s\bs,\b, o\bop\bp=\b=%\b%x\bx,\b, c\bcn\bnt\bt=\b=%\b%d\bd,\b, b\bbl\blo\boc\bck\bk=\b=%\b%d\bd.\b.  The driver en-
     tered an illegal state.  The information printed indicates the illegal
     state, the operation currently being executed, the I/O count, and the
     block number on the cassette.

     u\buu\bu%\b%d\bd:\b: b\bbr\bre\bea\bak\bk r\bre\bec\bce\bei\biv\bve\bed\bd,\b, t\btr\bra\ban\bns\bsf\bfe\ber\br r\bre\bes\bst\bta\bar\brt\bte\bed\bd.\b.  The TU58 was sending a contin-
     uous break signal and had to be reset. This may indicate a hardware prob-
     lem, but the driver will attempt to recover from the error.

     u\buu\bu%\b%d\bd r\bre\bec\bce\bei\biv\bve\be s\bst\bta\bat\bte\be e\ber\brr\bro\bor\br,\b, s\bst\bta\bat\bte\be=\b=%\b%s\bs,\b, b\bby\byt\bte\be=\b=%\b%x\bx.\b.  The driver entered an ille-
     gal state in the receiver finite state machine.  The state is shown along
     with the control byte of the received packet.

     u\buu\bu%\b%d\bd:\b: r\bre\bea\bad\bd s\bst\bta\bal\bll\ble\bed\bd.\b.  A timer watching the controller detected no inter-
     rupt for an extended period while an operation was outstanding.  This
     usually indicates that one or more receiver interrupts were lost and the
     transfer is restarted.

     u\buu\bu%\b%d\bd:\b: h\bha\bar\brd\bd e\ber\brr\bro\bor\br b\bbn\bn%\b%d\bd,\b, p\bpk\bk_\b_m\bmo\bod\bd %\b%o\bo.\b.  The device returned a status code in-
     dicating a hard error. The actual error code is shown in octal. No re-
     tries are attempted by the driver.

E\bER\bRR\bRO\bOR\bRS\bS
     The following errors may be returned:

     [ENXIO]  Nonexistent drive (on open); offset is too large or bad (unde-


              fined) ioctl(2) code.

     [EIO]    Open failed, the device could not be reset.

     [EBUSY]  Drive in use.

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     tu(4),  arff(8)

H\bHI\bIS\bST\bTO\bOR\bRY\bY
     The u\buu\bu driver appeared in 4.2BSD.

4.2 Berkeley Distribution        June 5, 1993                                2