1.\" $NetBSD: hpc.4,v 1.9 2006/07/20 13:23:29 rumble Exp $ 2.\" 3.\" Copyright (c) 2002 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This document is derived from work contributed to The NetBSD Foundation 7.\" by Antti Kantee. 8.\" 9.\" Redistribution and use in source and binary forms, with or without 10.\" modification, are permitted provided that the following conditions 11.\" are met: 12.\" 1. Redistributions of source code must retain the above copyright 13.\" notice, this list of conditions and the following disclaimer. 14.\" 2. Redistributions in binary form must reproduce the above copyright 15.\" notice, this list of conditions and the following disclaimer in the 16.\" documentation and/or other materials provided with the distribution. 17.\" 3. All advertising materials mentioning features or use of this software 18.\" must display the following acknowledgement: 19.\" This product includes software developed by the NetBSD 20.\" Foundation, Inc. and its contributors. 21.\" 4. Neither the name of The NetBSD Foundation nor the names of its 22.\" contributors may be used to endorse or promote products derived 23.\" from this software without specific prior written permission. 24.\" 25.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 26.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 27.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 28.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS BE 29.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 30.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 31.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 32.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 33.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 34.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 35.\" POSSIBILITY OF SUCH DAMAGE. 36.\" 37.Dd July 20, 2006 38.Dt HPC 4 sgimips 39.Os 40.Sh NAME 41.Nm hpc 42.Nd SGI High performance Peripheral Controller 43.Sh SYNOPSIS 44.Cd "hpc0 at gio0 addr 0x1fb80000 flags 0x0000" 45.Cd "hpc1 at gio0 addr 0x1fb00000 flags 0x0000" 46.Cd "hpc2 at gio0 addr 0x1fb98000 flags 0x0000" 47.Cd "hpc3 at gio0 addr 0x1fb90000 flags 0x0000" 48.Sh DESCRIPTION 49.Nm 50interfaces the peripherals connected to it to the 51.Xr gio 4 52bus. 53.Nm 54is found on the Personal Iris 4D/3x, Indigo, Indy, Challenge-S, and Indigo2 55machines. 56.Pp 57There are three different numerical revisions of the 58.Nm 59controller. 60Revisions 1 and 1.5 exist on Personal Iris 4D/3x and Indigo machines, 61as well as GIO32bis expansion cards such as the E++ SEEQ-based 62Ethernet adapter. 63Revision 1.5 supports bi-endian operation. 64Revision 3 exists on Indy and Indigo2 systems. 65It is possible to have an on-board HPC3 as well as HPC1.5-based 66GIO32bis adapters in the Indy. 67.Pp 68The 69.Nm 70driver will attempt to detect the revision present, but since 71this is a heuristic exercise, flags exist to force the detected 72revision: 73.Bl -tag -compact -width "0x0000" -offset "xxxx" 74.It 0x0001 75Force HPC Revision to 1 76.It 0x0002 77Force HPC Revision to 1.5 78.It 0x0003 79Force HPC Revision to 3 80.El 81.Sh HARDWARE 82.Bl -tag -width dsclock -offset indent 83.It dsclock 84DS1286-based RTC 85.It dpclock 86DP8573A-based RTC 87.It haltwo 88HAL2 audio controller 89.It sq 90Seeq 8003 and 80C03 91.Tn Ethernet 92controllers 93.It wdsc 94WD33c93 95.Tn SCSI 96controller 97.It zsc 98Zilog Z8530 UART 99.El 100.Sh SEE ALSO 101.Xr gio 4 , 102.Xr imc 4 , 103.Xr pic 4 104.Sh HISTORY 105The 106.Nm 107driver first appeared in 108.Nx 1.6 109with support for Revision 3. 110Revision 1 and 1.5 support was added in 111.Nx 2.0 . 112.Sh BUGS 113.Nm 114Revisions 1 and 1.5 support DMA buffer pointers of only 28 bits 115and may therefore only address 256 megabytes of memory. 116The R4k Indigo and Indy are the only systems that support sufficient 117memory to illustrate this drawback. 118A software workaround is not currently implemented. 119Revision 3, with 32 bit pointers, does not have this limitation. 120