1.\" Copyright (c) 1980, 1991 Regents of the University of California. 2.\" 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.\" from: @(#)tu.4 6.2 (Berkeley) 3/27/91 33.\" $Id: tu.4,v 1.2 1993/08/01 07:35:57 mycroft Exp $ 34.\" 35.Dd March 27, 1991 36.Dt TU 4 vax 37.Os BSD 4 38.Sh NAME 39.Nm tu 40.Nd 41.Tn VAX-11/730 42and 43.Tn VAX-11/750 44.Tn TU58 45console cassette interface 46.Sh SYNOPSIS 47.Cd "options MRSP" 48(for 49.Tn VAX-11/750 Ns 's 50with an 51.Tn MRSP 52prom) 53.Sh DESCRIPTION 54The 55.Nm tu 56interface provides access to the 57.Tn VAX 5811/730 and 11/750 59.Tn TU58 60console 61cassette drive(s). 62.Pp 63The interface supports only block 64.Tn I/O 65to the 66.Tn TU58 67cassettes. 68The devices are normally manipulated with the 69.Xr arff 8 70program using the ``f'' and ``m'' options. 71.Pp 72The device driver is automatically included when a 73system is configured to run on an 11/730 or 11/750. 74.Pp 75The 76.Tn TU58 77on an 11/750 uses the Radial Serial Protocol 78.Pq Tn RSP 79to communicate with the cpu over a serial line. This 80protocol is inherently unreliable as it has no flow 81control measures built in. On an 11/730 the Modified 82Radial Serial Protocol is used. This protocol incorporates 83flow control measures which insure reliable data transfer 84between the cpu and the device. Certain 11/750's have 85been modified to use the 86.Tn MRSP 87prom used in the 11/730. 88To reliably use the console 89.Tn TU58 90on an 11/750 under 91.Tn UNIX , 92the 93.Tn MRSP 94prom is required. For those 11/750's without 95an 96.Tn MRSP 97prom, an unreliable but often 98useable interface has been developed. 99This interface uses an assembly language ``pseudo-dma'' routine 100to minimize the receiver interrupt service latency. 101To include this code in 102the system, the configuration must 103.Em not 104specify the 105system will run on an 11/730 or use an 106.Tn MRSP 107prom. 108This unfortunately makes it impossible to configure a 109single system which will properly handle 110.Tn TU58 Ns 's 111on both an 11/750 112and an 11/730 (unless both machines have 113.Tn MRSP 114proms). 115.Sh FILES 116.Bl -tag -width /dev/tu0xx -compact 117.It Pa /dev/tu0 118.It Pa /dev/tu1 119(only on a 120.Tn VAX Ns \-11/730) 121.El 122.Sh DIAGNOSTICS 123.Bl -diag 124.It tu%d: no bp, active %d. 125A transmission complete interrupt was received with no outstanding 126.Tn I/O 127request. This indicates a hardware problem. 128.Pp 129.It "tu%d protocol error, state=%s, op=%x, cnt=%d, block=%d." 130The driver entered an illegal state. The information printed 131indicates the illegal state, operation currently being executed, 132the 133.Tn I/O 134count, and the block number on the cassette. 135.Pp 136.It "tu%d receive state error, state=%s, byte=%x." 137The driver entered an illegal state in the receiver finite 138state machine. The state is shown along with the control 139byte of the received packet. 140.Pp 141.It tu%d: read stalled. 142A timer watching the controller detected no interrupt for 143an extended period while an operation was outstanding. 144This usually indicates that one or more receiver interrupts 145were lost and the transfer is restarted (11/750 only). 146.Pp 147.It tu%d: hard error bn%d, pk_mod %o. 148The device returned a status code indicating a hard error. The 149actual error code is shown in octal. No retries are attempted 150by the driver. 151.El 152.Sh SEE ALSO 153.Xr arff 8 154.Sh HISTORY 155The 156.Nm 157driver appeared in 158.Bx 4.1 . 159.Sh BUGS 160The 161.Tn VAX Ns \-11/750 162console interface without 163.Tn MRSP 164prom is unuseable 165while the system is multi-user; it should be used only with 166the system running single-user and, even then, with caution. 167