BSD 4_4 development
[unix-history] / usr / share / man / cat4 / vax / tu.0
TU(4) BSD Programmer's Manual (VAX Architecture) TU(4)
N\bNA\bAM\bME\bE
t\btu\bu - VAX-11/730 and VAX-11/750 TU58 console cassette interface
S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
o\bop\bpt\bti\bio\bon\bns\bs M\bMR\bRS\bSP\bP
(for VAX-11/750's with an MRSP prom)
D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
The t\btu\bu interface provides access to the VAX 11/730 and 11/750 TU58 con-
sole cassette drive(s).
The interface supports only block I/O to the TU58 cassettes. The devices
are normally manipulated with the arff(8) program using the ``f'' and
``m'' options.
The device driver is automatically included when a system is configured
to run on an 11/730 or 11/750.
The TU58 on an 11/750 uses the Radial Serial Protocol (RSP) to communi-
cate with the cpu over a serial line. This protocol is inherently unre-
liable as it has no flow control measures built in. On an 11/730 the
Modified Radial Serial Protocol is used. This protocol incorporates flow
control measures which insure reliable data transfer between the cpu and
the device. Certain 11/750's have been modified to use the MRSP prom
used in the 11/730. To reliably use the console TU58 on an 11/750 under
UNIX, the MRSP prom is required. For those 11/750's without an MRSP
prom, an unreliable but often useable interface has been developed. This
interface uses an assembly language ``pseudo-dma'' routine to minimize
the receiver interrupt service latency. To include this code in the sys-
tem, the configuration must _\bn_\bo_\bt specify the system will run on an 11/730
or use an MRSP prom. This unfortunately makes it impossible to configure
a single system which will properly handle TU58's on both an 11/750 and
an 11/730 (unless both machines have MRSP proms).
F\bFI\bIL\bLE\bES\bS
/dev/tu0
/dev/tu1 (only on a VAX-11/730)
D\bDI\bIA\bAG\bGN\bNO\bOS\bST\bTI\bIC\bCS\bS
t\btu\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.
t\btu\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, operation currently being executed, the I/O count, and the block
number on the cassette.
t\btu\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.
t\btu\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 (11/750 only).
t\btu\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.
S\bSE\bEE\bE A\bAL\bLS\bSO\bO
arff(8)
H\bHI\bIS\bST\bTO\bOR\bRY\bY
The t\btu\bu driver appeared in 4.1BSD.
B\bBU\bUG\bGS\bS
The VAX-11/750 console interface without MRSP prom is unuseable while the
system is multi-user; it should be used only with the system running sin-
gle-user and, even then, with caution.
4th Berkeley Distribution June 5, 1993 2