1 files changed, 0 insertions, 73 deletions
diff --git a/static/netbsd/man4/man4.sgimips/gio.4 3.html b/static/netbsd/man4/man4.sgimips/gio.4 3.html
deleted file mode 100644
index ff5b3d6e..00000000
--- a/static/netbsd/man4/man4.sgimips/gio.4 3.html
+++ /dev/null
@@ -1,73 +0,0 @@
-<table class="head">
-  <tr>
-    <td class="head-ltitle">GIO(4)</td>
-    <td class="head-vol">Device Drivers Manual (sgimips)</td>
-    <td class="head-rtitle">GIO(4)</td>
-  </tr>
-</table>
-<div class="manual-text">
-<section class="Sh">
-<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
-<p class="Pp"><code class="Nm">gio</code> &#x2014; <span class="Nd">SGI's
-    Graphics I/O (GIO) bus (an early PCI-like bus)</span></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
-<p class="Pp"><code class="Cd">gio0 at imc0</code>
-  <br/>
-  <code class="Cd">gio0 at pic0</code></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
-<p class="Pp">The <code class="Nm">gio</code> 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
-    <a class="Xr">sgimips/hpc(4)</a> peripheral controller, and memory and CPU
-    are accessed through the <a class="Xr">sgimips/imc(4)</a> (Indy Memory
-    Controller) or <a class="Xr">sgimips/pic(4)</a> (Processor Interface
-    Controller). The <code class="Nm">gio</code> 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.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
-  ALSO</a></h1>
-<p class="Pp"><a class="Xr">sgimips/giopci(4)</a>,
-    <a class="Xr">sgimips/grtwo(4)</a>, <a class="Xr">sgimips/hpc(4)</a>,
-    <a class="Xr">sgimips/imc(4)</a>, <a class="Xr">sgimips/light(4)</a>,
-    <a class="Xr">sgimips/newport(4)</a>, <a class="Xr">sgimips/pic(4)</a></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
-<p class="Pp">The <code class="Nm">gio</code> driver first appeared in
-    <span class="Ux">NetBSD 1.5</span>.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1>
-<p class="Pp">Challenge S systems may use only one <code class="Nm">gio</code>
-    DMA-capable expansion card, despite having two slots. Cards based on the
-    <a class="Xr">sgimips/hpc(4)</a> 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).</p>
-<p class="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.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
-<p class="Pp">Systems employing the <a class="Xr">sgimips/imc(4)</a> 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.</p>
-</section>
-</div>
-<table class="foot">
-  <tr>
-    <td class="foot-date">February 17, 2017</td>
-    <td class="foot-os">NetBSD 10.1</td>
-  </tr>
-</table>