BSD 4_3_Net_2 release

[unix-history] / usr / src / share / man / man4 / man4.tahoe / cy.4

diff --git a/usr/src/share/man/man4/man4.tahoe/cy.4 b/usr/src/share/man/man4/man4.tahoe/cy.4
index d25f8ef..7c87a96 100644 (file)
--- a/usr/src/share/man/man4/man4.tahoe/cy.4
+++ b/usr/src/share/man/man4/man4.tahoe/cy.4
@@ -1,128 +1,174 @@
-.\" Copyright (c) 1986 Regents of the University of California.
-.\" All rights reserved.  The Berkeley software License Agreement
-.\" specifies the terms and conditions for redistribution.
+.\" Copyright (c) 1986, 1991 Regents of the University of California.
+.\" All rights reserved.

 .\"
 .\"

-.\"    @(#)cy.4        6.3 (Berkeley) 7/8/88
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"    This product includes software developed by the University of
+.\"    California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.

 .\"
 .\"

-.TH CY 4 "July 8, 1988"
-.UC 7
-.SH NAME
-cy \- Cipher/tapemaster magtape interface
-.SH SYNOPSIS
-.B "controller cy0 at vba? csr 0xffff4000 vector cyintr"
-.br
-.B "device yc0 at cy0 drive 0"
-.SH DESCRIPTION
-The Cipher F880, M990/Tapemaster combination provides a standard tape drive
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)cy.4       6.4 (Berkeley) 3/27/91
+.\"
+.Dd March 27, 1991
+.Dt CY 4 tahoe
+.Os BSD 4.3t
+.Sh NAME
+.Nm cy
+.Nd Cipher/tapemaster magtape interface
+.Sh SYNOPSIS
+.Cd "controller cy0 at vba? csr 0xffff4000 vector cyintr"
+.Cd "device yc0 at cy0 drive 0"
+.Sh DESCRIPTION
+The Cipher
+.Tn F880 ,
+.Tn M990 Ns / Tapemaster
+combination provides a standard tape drive

 interface as described in
 interface as described in

-.IR mt (4).
-The Cipher F880 tape drive operates at 1600 or 3200 bpi \-
+.Xr mt 4 .
+The Cipher
+.Tn F880
+tape drive operates at 1600 or 3200
+.Tn BPI \-

 controlled by a switch on the drive. 
 controlled by a switch on the drive. 

-The Cipher M990 operates at 1600, 3200 or 6250 bpi \-
+The Cipher
+.Tn M990
+operates at 1600, 3200 or 6250
+.Tn BPI \-

 controlled by switches on the front of the drive.
 controlled by switches on the front of the drive.

-.PP
+.Pp

 The Tapemaster controller board is actually a Multibus controller
 The Tapemaster controller board is actually a Multibus controller

-accessed through a Halversa Multibus to VERSAbus converter card.
-.SH "SEE ALSO"
-mt(1), tar(1), mtio(4)
-.SH DIAGNOSTICS
-\fBcy%d: %dkb buffer\fP.  The formatter was found to have a
-%d kilobyte buffer during autoconfiguration.
-.PP
-\fBcy%d: timeout or err during init, status=%b\fP.  The controller
+accessed through a Halversa Multibus to
+.Tn VERSAbus
+converter card.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It cy%d: %dkb buffer.
+The formatter was found to have a
+.Ql %d
+kilobyte buffer during autoconfiguration.
+.It cy%d: timeout or err during init, status=%b.
+The controller

 timed out or an error occurred on a nop command during autoconfiguration;
 the controller may be hung.
 timed out or an error occurred on a nop command during autoconfiguration;
 the controller may be hung.

-.PP
-\fBcy%d: configuration failure, status=%b\fP.  The controller
+.It cy%d: configuration failure, status=%b.
+The controller

 timed out or an error occurred on a configure command during
 autoconfiguration; the controller may be hung.
 timed out or an error occurred on a configure command during
 autoconfiguration; the controller may be hung.

-.PP
-\fByc%d: no write ring\fR.  An attempt was made to write on the tape drive
+.It yc%d: no write ring.
+An attempt was made to write on the tape drive

 when no write ring was present; this message is written on the terminal of
 the user who tried to access the tape.
 when no write ring was present; this message is written on the terminal of
 the user who tried to access the tape.

-.PP
-\fByc%d: not online\fR.  An attempt was made to access the tape while it
+.It yc%d: not online.
+An attempt was made to access the tape while it

 was offline; this message is written on the terminal of the user
 who tried to access the tape.
 was offline; this message is written on the terminal of the user
 who tried to access the tape.

-.PP
-\fBcy%d: i/o size too large\fP.  A read or a write request exceeded the
+.It cy%d: i/o size too large.
+A read or a write request exceeded the

 maximum transfer size for the controller \- 32 kilobytes; this message
 is written on the terminal of the user who made the read or write request.
 maximum transfer size for the controller \- 32 kilobytes; this message
 is written on the terminal of the user who made the read or write request.

-.PP
-\fByc%d: hard error bn%d status=%b\fR.   A tape error occurred
-at block \fIbn\fR; the cy error register is
+.It yc%d: hard error bn%d status=%b.
+A tape error occurred
+at block
+.Em bn ;
+the cy error register is

 printed in hexadecimal with the bits symbolically decoded.  Any error is
 fatal on non-raw tape; when possible the driver will have retried
 the operation which failed several times before reporting the error.
 printed in hexadecimal with the bits symbolically decoded.  Any error is
 fatal on non-raw tape; when possible the driver will have retried
 the operation which failed several times before reporting the error.

-For known errors, the trailing %s is one of the following:
-.RS
-\fBtimeout\fP, \fBtimeout1\fP, \fBtimeout2\fP, \fBtimeout3\fP, \fBtimeout4\fP. 
+For known errors, the trailing
+.Ql %s
+is one of the following:
+.Pp
+.Bl -diag -offset indent -compact
+.It timeout, timeout1, timeout2, timeout3, timeout4.

 Time out errors; this may be due to trying to read a blank tape
 or the controller failing to interrupt or the drive dropping off-line.
 Time out errors; this may be due to trying to read a blank tape
 or the controller failing to interrupt or the drive dropping off-line.

-.PP
-\fBnon-existent memory\fP.  A controller transfer to memory timed out.
-.PP
-\fBblank tape\fP.  The controller detected a blank tape when
+.It non-existent memory.
+A controller transfer to memory timed out.
+.It blank tape.
+The controller detected a blank tape when

 data was expected.
 data was expected.

-.PP
-\fBmicro-diagnostic\fP, \fBmissing diagnostic jumper\fP. 
+.It micro-diagnostic, missing diagnostic jumper.

 An error occurred in the micro-diagnostics or
 the diagnostic mode jumper was not installed while attempting to execute
 a diagnostics command.
 An error occurred in the micro-diagnostics or
 the diagnostic mode jumper was not installed while attempting to execute
 a diagnostics command.

-.PP
-\fBeot/bot detected\fP.  The controller unexpectedly encountered
+.It eot/bot detected.
+The controller unexpectedly encountered

 end-of-tape or beginning-of-tape during an operation.
 end-of-tape or beginning-of-tape during an operation.

-.PP
-\fBretry unsuccessful\fP.  
+.It retry unsuccessful.

 An error occurred which could not be recovered by repeated retries.
 An error occurred which could not be recovered by repeated retries.

-.PP
-\fBfifo over/under-flow\fP.
+.It fifo over/under-flow.

 The controller was unable to transfer data to the drive fast enough.
 This usually occurs because a transfer was performed without using the
 controller's internal buffer.
 The controller was unable to transfer data to the drive fast enough.
 This usually occurs because a transfer was performed without using the
 controller's internal buffer.

-.PP
-\fBdrive to controller parity error\fP.
+.It drive to controller parity error.

 A parity error was detected by the controller in data transferred
 between the drive and the controller's internal buffer.
 A parity error was detected by the controller in data transferred
 between the drive and the controller's internal buffer.

-.PP
-\fBprom checksum\fP.
-The controller thinks its PROM is corrupted.
-.PP
-\fBtime out tape strobe (record length error)\fP.
+.It prom checksum.
+The controller thinks its
+.Tn PROM
+is corrupted.
+.It time out tape strobe (record length error).

 The controller timed out while looking for an inter-record gap.
 This usually occurs because the records on the tape are larger than
 expected (or can be handled).
 The controller timed out while looking for an inter-record gap.
 This usually occurs because the records on the tape are larger than
 expected (or can be handled).

-.PP
-\fBtape not ready\fP.
+.It tape not ready.

 The drive does not respond; usually the power has been turned off
 or a cable has come off.
 The drive does not respond; usually the power has been turned off
 or a cable has come off.

-.PP
-\fBwrite protected\fP.
+.It write protected.

 A write ring was present in the tape when a write was attempted.
 A write ring was present in the tape when a write was attempted.

-.PP
-\fBinvalid link pointer\fP.
+.It invalid link pointer.

 An invalid pointer was encountered in a tape parameter block.
 An invalid pointer was encountered in a tape parameter block.

-.PP
-\fBunexpected file mark\fP.
+.It unexpected file mark.

 A tape file mark was encountered while trying to read or space.
 A tape file mark was encountered while trying to read or space.

-.PP
-\fBinvalid byte count\fP.
+.It invalid byte count.

 An invalid byte count parameter was encountered in a tape parameter
 block.
 An invalid byte count parameter was encountered in a tape parameter
 block.

-.PP
-\fBunidentified hardware error\fP, \fBstreaming terminated\fP.
+.It unidentified hardware error.
+.It streaming terminated.

 These should not happen.
 These should not happen.

-.RE
-.PP
-\fByc%d: lost interrupt\fP.
+.El
+.Pp
+.It yc%d: lost interrupt.

 The controller failed to respond with an interrupt signifying completion
 of the current command.  The system will attempt to abort the
 outstanding command and reset the controller.
 The controller failed to respond with an interrupt signifying completion
 of the current command.  The system will attempt to abort the
 outstanding command and reset the controller.

-.PP
-\fBcy%d: reset failed\fP.
+.Pp
+.It cy%d: reset failed.

 The system was unable to reset the controller.  This is normally preceded
 by another message from the driver.
 The system was unable to reset the controller.  This is normally preceded
 by another message from the driver.

-.SH BUGS
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr mtio 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 tahoe .
+.Sh BUGS

 The controller supports only 20-bit addresses.  The only way the
 system can insure the controller will be able to address data
 to be transferred
 The controller supports only 20-bit addresses.  The only way the
 system can insure the controller will be able to address data
 to be transferred