1.\" Copyright (c) 1980, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by the University of 15.\" California, Berkeley and its contributors. 16.\" 4. Neither the name of the University nor the names of its contributors 17.\" may be used to endorse or promote products derived from this software 18.\" without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)tu.4 8.1 (Berkeley) 6/5/93 33.\" 34.Dd June 5, 1993 35.Dt TU 4 vax 36.Os BSD 4 37.Sh NAME 38.Nm tu 39.Nd 40.Tn VAX-11/730 41and 42.Tn VAX-11/750 43.Tn TU58 44console cassette interface 45.Sh SYNOPSIS 46.Cd "options MRSP" 47(for 48.Tn VAX-11/750 Ns 's 49with an 50.Tn MRSP 51prom) 52.Sh DESCRIPTION 53The 54.Nm tu 55interface provides access to the 56.Tn VAX 5711/730 and 11/750 58.Tn TU58 59console 60cassette drive(s). 61.Pp 62The interface supports only block 63.Tn I/O 64to the 65.Tn TU58 66cassettes. 67The devices are normally manipulated with the 68.Xr arff 8 69program using the ``f'' and ``m'' options. 70.Pp 71The device driver is automatically included when a 72system is configured to run on an 11/730 or 11/750. 73.Pp 74The 75.Tn TU58 76on an 11/750 uses the Radial Serial Protocol 77.Pq Tn RSP 78to communicate with the cpu over a serial line. This 79protocol is inherently unreliable as it has no flow 80control measures built in. On an 11/730 the Modified 81Radial Serial Protocol is used. This protocol incorporates 82flow control measures which insure reliable data transfer 83between the cpu and the device. Certain 11/750's have 84been modified to use the 85.Tn MRSP 86prom used in the 11/730. 87To reliably use the console 88.Tn TU58 89on an 11/750 under 90.Tn UNIX , 91the 92.Tn MRSP 93prom is required. For those 11/750's without 94an 95.Tn MRSP 96prom, an unreliable but often 97useable interface has been developed. 98This interface uses an assembly language ``pseudo-dma'' routine 99to minimize the receiver interrupt service latency. 100To include this code in 101the system, the configuration must 102.Em not 103specify the 104system will run on an 11/730 or use an 105.Tn MRSP 106prom. 107This unfortunately makes it impossible to configure a 108single system which will properly handle 109.Tn TU58 Ns 's 110on both an 11/750 111and an 11/730 (unless both machines have 112.Tn MRSP 113proms). 114.Sh FILES 115.Bl -tag -width /dev/tu0xx -compact 116.It Pa /dev/tu0 117.It Pa /dev/tu1 118(only on a 119.Tn VAX Ns \-11/730) 120.El 121.Sh DIAGNOSTICS 122.Bl -diag 123.It tu%d: no bp, active %d. 124A transmission complete interrupt was received with no outstanding 125.Tn I/O 126request. This indicates a hardware problem. 127.Pp 128.It "tu%d protocol error, state=%s, op=%x, cnt=%d, block=%d." 129The driver entered an illegal state. The information printed 130indicates the illegal state, operation currently being executed, 131the 132.Tn I/O 133count, and the block number on the cassette. 134.Pp 135.It "tu%d receive state error, state=%s, byte=%x." 136The driver entered an illegal state in the receiver finite 137state machine. The state is shown along with the control 138byte of the received packet. 139.Pp 140.It tu%d: read stalled. 141A timer watching the controller detected no interrupt for 142an extended period while an operation was outstanding. 143This usually indicates that one or more receiver interrupts 144were lost and the transfer is restarted (11/750 only). 145.Pp 146.It tu%d: hard error bn%d, pk_mod %o. 147The device returned a status code indicating a hard error. The 148actual error code is shown in octal. No retries are attempted 149by the driver. 150.El 151.Sh SEE ALSO 152.Xr arff 8 153.Sh HISTORY 154The 155.Nm 156driver appeared in 157.Bx 4.1 . 158.Sh BUGS 159The 160.Tn VAX Ns \-11/750 161console interface without 162.Tn MRSP 163prom is unuseable 164while the system is multi-user; it should be used only with 165the system running single-user and, even then, with caution. 166