Training courses

Kernel and Embedded Linux

Bootlin training courses

Embedded Linux, kernel,
Yocto Project, Buildroot, real-time,
graphics, boot time, debugging...

Bootlin logo

Elixir Cross Referencer

.\"	$NetBSD: gio.4,v 1.21 2017/02/17 22:24:47 christos Exp $
.\"
.\" Copyright (c) 2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" This document is derived from work contributed to The NetBSD Foundation
.\" by Antti Kantee.
.\"
.\" 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.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. 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 FOUNDATION 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.
.\"
.Dd February 17, 2017
.Dt GIO 4 sgimips
.Os
.Sh NAME
.Nm gio
.Nd SGI's Graphics I/O (GIO) bus (an early PCI-like bus)
.Sh SYNOPSIS
.Cd "gio0 at imc0"
.Cd "gio0 at pic0"
.Sh DESCRIPTION
The
.Nm
bus is a bus for connecting high-speed peripherals to the main memory and
CPU.
The devices themselves are typically (but not necessarily) connected to the
.Xr sgimips/hpc 4
peripheral controller, and memory and CPU are accessed through the
.Xr sgimips/imc 4
(Indy Memory Controller) or
.Xr sgimips/pic 4
(Processor Interface Controller).
The
.Nm
bus is found on the Personal Iris 4D/3x, Indigo, Indy, Challenge S,
Challenge M, and Indigo2 machines and exists in three incarnations:
GIO32, GIO32-bis, and GIO64.
.Sh SEE ALSO
.Xr sgimips/giopci 4 ,
.Xr sgimips/grtwo 4 ,
.Xr sgimips/hpc 4 ,
.Xr sgimips/imc 4 ,
.Xr sgimips/light 4 ,
.Xr sgimips/newport 4 ,
.Xr sgimips/pic 4
.Sh HISTORY
The
.Nm
driver first appeared in
.Nx 1.5 .
.Sh CAVEATS
Challenge S systems may use only one
.Nm
DMA-capable expansion card, despite having two slots.
Cards based on the
.Xr sgimips/hpc 4
controller, such as the GIO32 scsi and E++ Ethernet adapters, must be
placed in slot 1 (closest to the side of the case).
All other cards must be placed in slot 0 (adjacent to the memory banks).
.Pp
Indigo2 and Challenge M systems contain either three or four GIO64 connectors,
depending on the model.
However, in both cases only two electrically
distinct slots are present.
Therefore, distinct expansion cards may not
share physical connectors associated with the same slot.
Refer to the PCB
stencils to determine the association between physical connectors and slots.
.Sh BUGS
Systems employing the
.Xr sgimips/imc 4
may experience spurious SysAD bus parity errors when using expansion cards,
which do not drive all data lines during a CPU PIO read.
The only workaround is to disable SysAD parity checking when using such
cards.