1.\" $NetBSD: hpc.4,v 1.8 2004/08/16 10:48:43 wiz 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 August 15, 2004 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, and Indigo2 machines. 55.Pp 56There are three different numerical revisions of the 57.Nm 58controller. 59Revisions 1 and 1.5 exist on Personal Iris 4D/3x and Indigo machines, 60as well as GIO32bis expansion cards such as the E++ SEEQ-based 61Ethernet adapter. 62Revision 1.5 supports bi-endian operation. 63Revision 3 exists on Indy and Indigo2 systems. 64It is possible to have an on-board HPC3 as well as HPC1.5-based 65GIO32bis adapters in the Indy. 66.Pp 67The 68.Nm 69driver will attempt to detect the revision present, but since 70this is a heuristic exercise, flags exist to force the detected 71revision: 72.Bl -tag -compact -width "0x0000" -offset "xxxx" 73.It 0x0001 74Force HPC Revision to 1 75.It 0x0002 76Force HPC Revision to 1.5 77.It 0x0003 78Force HPC Revision to 3 79.El 80.Sh HARDWARE 81.Bl -tag -width dsclock -offset indent 82.It dsclock 83DS1286-based RTC 84.It dpclock 85DP8573A-based RTC 86.It haltwo 87HAL2 audio controller 88.It sq 89Seeq 8003 and 80C03 90.Tn Ethernet 91controllers 92.It wdsc 93WD33c93 94.Tn SCSI 95controller 96.It zsc 97Zilog Z8530 UART 98.El 99.Sh SEE ALSO 100.Xr gio 4 , 101.Xr imc 4 , 102.Xr pic 4 103.Sh HISTORY 104The 105.Nm 106driver first appeared in 107.Nx 1.6 108with support for Revision 3. 109Revision 1 and 1.5 support was added in 110.Nx 2.0 . 111.Sh BUGS 112.Nm 113Revisions 1 and 1.5 support DMA buffer pointers of only 28 bits 114and may therefore only address 256 megabytes of memory. 115The R4k Indigo and Indy are the only systems that support sufficient 116memory to illustrate this drawback. 117A software workaround is not currently implemented. 118Revision 3, with 32 bit pointers, does not have this limitation. 119