summaryrefslogtreecommitdiff
path: root/share/man/man4/man4.vax/uda.4
diff options
context:
space:
mode:
Diffstat (limited to 'share/man/man4/man4.vax/uda.4')
-rw-r--r--share/man/man4/man4.vax/uda.453
1 files changed, 14 insertions, 39 deletions
diff --git a/share/man/man4/man4.vax/uda.4 b/share/man/man4/man4.vax/uda.4
index c07bc33e32a..4bf2ab59386 100644
--- a/share/man/man4/man4.vax/uda.4
+++ b/share/man/man4/man4.vax/uda.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: uda.4,v 1.23 2015/02/15 22:26:45 bentley Exp $
+.\" $OpenBSD: uda.4,v 1.24 2015/09/10 15:16:43 schwarze Exp $
.\" $NetBSD: uda.4,v 1.3 1996/03/03 17:14:10 thorpej Exp $
.\"
.\" Copyright (c) 1980, 1987, 1991 Regents of the University of California.
@@ -30,28 +30,21 @@
.\"
.\" from: @(#)uda.4 6.6 (Berkeley) 3/27/91
.\"
-.Dd $Mdocdate: February 15 2015 $
+.Dd $Mdocdate: September 10 2015 $
.Dt UDA 4 vax
.Os
.Sh NAME
.Nm uda
-.Nd
-.Tn UDA50
-disk controller interface
+.Nd UDA50 disk controller interface
.Sh SYNOPSIS
.Cd "uda0 at uba? csr 0172150"
.Cd "uda1 at uba? csr 0160334"
.Cd "mscpbus* at uda?"
.Sh DESCRIPTION
-This is a driver for the
-.Tn DEC UDA50
-disk controller and other
+This is a driver for the DEC UDA50 disk controller and other
compatible controllers.
-The
-.Tn UDA50
-communicates with the host through
-a packet protocol known as the Mass Storage Control Protocol
-.Pq Tn MSCP .
+The UDA50 communicates with the host through
+a packet protocol known as the Mass Storage Control Protocol (MSCP).
Consult the file
.In vax/mscp.h
for a detailed description of this protocol.
@@ -262,10 +255,7 @@ The controller reported an error.
The error code is printed in
octal, along with a short description if the code is known (see the
.%T UDA50 Maintenance Guide ,
-.Tn DEC
-part number
-.Tn AA-M185B-TC ,
-pp. 18-22).
+DEC part number AA-M185B-TC, pp. 18-22).
If this occurs during normal
operation, the driver will reset it and retry pending I/O.
If
@@ -279,9 +269,7 @@ The driver will retry initialization later.
.It "uda0: version X model Y"
An informational message giving the revision level of the controller.
.It "uda0: DMA burst size set to N"
-An informational message showing the
-.Tn DMA
-burst size, in words.
+An informational message showing the DMA burst size, in words.
.It "uda0: SETCTLRC failed: `detail'"
The Set Controller Characteristics command (the last part of the
controller initialization sequence) failed.
@@ -302,12 +290,8 @@ The
.Em detail
message should tell why.
.It "panic: udareplace"
-The controller reported completion of a
-.Tn REPLACE
-operation.
-The driver never issues any
-.Tn REPLACE Ns s ,
-so something is wrong.
+The controller reported completion of a REPLACE operation.
+The driver never issues any REPLACE operations, so something is wrong.
.It "panic: udabb"
The controller reported completion of bad block related I/O.
The
@@ -385,8 +369,7 @@ read.
A typical disk error; the retry count and error recovery levels are
printed, along with the block type (`lbn', or logical block; or `rbn',
or replacement block) and number.
-If the string is something else,
-.Tn DEC
+If the string is something else, DEC
has been clever, or your hardware has gone to Australia for vacation
(unless you live there; then it might be in New Zealand, or Brazil).
.It unit N: ... N
@@ -443,11 +426,7 @@ The Format Control
Table cannot be read (`fct unread - edc'), there is a bad sector
header (`invalid sector header'), the drive is not set for 512-byte
sectors (`not 512 sectors'), the drive is not formatted (`not formatted'),
-or the
-.Tn FCT
-has an uncorrectable
-.Tn ECC
-error (`fct ecc').
+or the FCT has an uncorrectable ECC error (`fct ecc').
.It "write protected (...) (code 6, subcode N)"
The drive is write protected, either by the front panel switch
(`hardware') or via the driver (`software').
@@ -466,13 +445,9 @@ no bad block replacement, so these should not occur.
A `header compare' error probably means the block is shot.
A `sync timeout' presumably has something to do with sector synchronisation.
An `uncorrectable ecc' error is an ordinary data error that cannot
-be fixed via
-.Tn ECC
-logic.
+be fixed via ECC logic.
A `N symbol ecc' error is a data error
-that can be (and presumably has been) corrected by the
-.Tn ECC
-logic.
+that can be (and presumably has been) corrected by the ECC logic.
It might indicate a sector that is imperfect but usable, or that
is starting to go bad.
If any of these errors recur, the sector