summaryrefslogtreecommitdiff
path: root/share/man/man4/man4.sgi/hpc.4
diff options
context:
space:
mode:
authorJason McIntyre <jmc@cvs.openbsd.org>2012-03-29 08:47:36 +0000
committerJason McIntyre <jmc@cvs.openbsd.org>2012-03-29 08:47:36 +0000
commit90a8c2409ca7988692f1164fb916f72749d84975 (patch)
treeda06b4b3b63cf85280f33270938305b5036a3798 /share/man/man4/man4.sgi/hpc.4
parent15d2046c3a68bb38fd9fb52751ed9e3bf3e0c78d (diff)
tweak previous;
Diffstat (limited to 'share/man/man4/man4.sgi/hpc.4')
-rw-r--r--share/man/man4/man4.sgi/hpc.414
1 files changed, 7 insertions, 7 deletions
diff --git a/share/man/man4/man4.sgi/hpc.4 b/share/man/man4/man4.sgi/hpc.4
index c996ce17f38..ad259a038ed 100644
--- a/share/man/man4/man4.sgi/hpc.4
+++ b/share/man/man4/man4.sgi/hpc.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: hpc.4,v 1.4 2012/03/28 20:44:23 miod Exp $
+.\" $OpenBSD: hpc.4,v 1.5 2012/03/29 08:47:35 jmc Exp $
.\" $NetBSD: hpc.4,v 1.12 2008/04/30 13:10:56 martin Exp $
.\"
.\" Copyright (c) 2002 The NetBSD Foundation, Inc.
@@ -28,7 +28,7 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
-.Dd $Mdocdate: March 28 2012 $
+.Dd $Mdocdate: March 29 2012 $
.Dt HPC 4 sgi
.Os
.Sh NAME
@@ -64,10 +64,10 @@ Additionally, the Challenge S may have a secondary HPC3 if the IOPLUS
The devices currently supported are:
.Pp
.Bl -tag -width 10n -offset 3n -compact
-.It Xr dsclock 4
-DS1286 realtime clock
.It Xr dpclock 4
DP8573A realtime clock
+.It Xr dsclock 4
+DS1286 realtime clock
.\" .It Xr haltwo 4
.\" HAL2 audio controller
.It Xr sq 4
@@ -75,7 +75,7 @@ Seeq 8003/80C03 Ethernet controller
.It Xr wdsc 4
WD33c93 SCSI controller
.It Xr zs 4
-Zilog Z8530 UART
+Zilog 8530 (ZSCC) Serial Communications Controller
.El
.Sh SEE ALSO
.Xr gio 4 ,
@@ -83,9 +83,9 @@ Zilog Z8530 UART
.Xr intro 4
.Sh BUGS
.Nm
-Revisions 1 and 1.5 support DMA buffer pointers of only 28 bits
+revisions 1 and 1.5 support DMA buffer pointers of only 28 bits
and may therefore only address 256 megabytes of memory.
The R4k Indigo and Indy are the only systems that support sufficient
memory to illustrate this drawback.
A software workaround is not currently implemented.
-Revision 3, with 32 bit pointers, does not have this limitation.
+Revision 3, with 32-bit pointers, does not have this limitation.