docs: Removed Precompiled HTML

1 files changed, 0 insertions, 450 deletions

diff --git a/static/netbsd/man4/ath.4 3.html b/static/netbsd/man4/ath.4 3.html
deleted file mode 100644
index 8f6ebddd..00000000
--- a/static/netbsd/man4/ath.4 3.html
+++ /dev/null
@@ -1,450 +0,0 @@
-<table class="head">
-  <tr>
-    <td class="head-ltitle">ATH(4)</td>
-    <td class="head-vol">Device Drivers Manual</td>
-    <td class="head-rtitle">ATH(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">ath</code> &#x2014; <span class="Nd">Atheros IEEE
-    802.11 driver</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">ath* at pci? dev ? function ?</code>
-  <br/>
-  <code class="Cd">ath* at cardbus? function ?</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">ath</code> driver provides support for
-    wireless network adapters based on the Atheros AR2413, AR2417, AR5210,
-    AR5211, AR5212, AR5213, AR5413, AR5416, AR5424, AR9160, AR9280, and AR9285
-    chips. Chip-specific support is provided by the Atheros Hardware Access
-    Layer (HAL).</p>
-<p class="Pp">Supported features include 802.11 and 802.3 frames, power
-    management, BSS, IBSS, and host-based access point operation modes. All
-    host/device interaction is via DMA.</p>
-<p class="Pp">The <code class="Nm">ath</code> driver encapsulates all IP and ARP
-    traffic as 802.11 frames, however it can receive either 802.11 or 802.3
-    frames. Transmit speed and operating mode is selectable depending on your
-    hardware.</p>
-<p class="Pp">AR5210-based devices support 802.11a operation with transmit
-    speeds of 6 Mbps, 9 Mbps, 12 Mbps, 18 Mbps, 24 Mbps, 36 Mbps, 48 Mbps, and
-    54 Mbps.</p>
-<p class="Pp">AR5211-based devices support 802.11a and 802.11b operation with
-    transmit speeds as above for 802.11a operation and 1Mbps, 2Mbps, 5.5 Mbps
-    and 11Mbps for 802.11b operation.</p>
-<p class="Pp">AR5212-based and AR5213-based devices support 802.11a, 802.11b,
-    and 802.11g operation with transmit speeds appropriate to each.</p>
-<p class="Pp">All chips also support an Atheros Turbo Mode (TM) that operates in
-    the 802.11a frequency range with 2x the transmit speeds. (This mode is,
-    however, only interoperable with other Atheros-based devices.)</p>
-<p class="Pp">The actual transmit speed used is dependent on signal quality and
-    the &#x201C;rate control&#x201D; algorithm employed by the driver. All chips
-    support WEP encryption.</p>
-<p class="Pp">By default, the <code class="Nm">ath</code> driver configures the
-    card for BSS operation (aka infrastructure mode). This mode requires the use
-    of an access point (base station).</p>
-<p class="Pp">The <code class="Nm">ath</code> driver also supports the standard
-    IBSS point-to-point mode where stations can communicate amongst themselves
-    without the aid of an access point.</p>
-<p class="Pp">The driver may also be configured to operate in hostap mode. In
-    this mode a host may function as an access point (base station). Access
-    points are different than operating in IBSS mode. They operate in BSS mode.
-    They allow for easier roaming and bridge all Ethernet traffic such that
-    machines connected via an access point appear to be on the local Ethernet
-    segment.</p>
-<p class="Pp">The mode of operation is chosen by specifying the appropriate
-    mediaopt value to ifconfig. The <code class="Fl">-m</code> flag to ifconfig
-    will list the available options.</p>
-<p class="Pp">For more information on configuring this device, see
-    <a class="Xr">ifconfig(8)</a>.</p>
-<p class="Pp">Devices supported by the <code class="Nm">ath</code> driver come
-    in either CardBus or mini-PCI packages. Wireless cards in CardBus slots may
-    be inserted and ejected on the fly.</p>
-<p class="Pp">The following cards are among those supported by the
-    <code class="Nm">ath</code> driver:</p>
-<p class="Pp"></p>
-<table class="Bl-column Bl-compact">
-  <tr id="Card">
-    <td><a class="permalink" href="#Card"><i class="Em">Card</i></a></td>
-    <td>Chip</td>
-    <td>Bus</td>
-    <td>Standard</td>
-  </tr>
-  <tr>
-    <td>3Com 3CRPAG175</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Airlink AWLH4030</td>
-    <td>AR5212</td>
-    <td>PCI</td>
-    <td>b/g</td>
-  </tr>
-  <tr>
-    <td>Aztech WL830PC</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>b/g</td>
-  </tr>
-  <tr>
-    <td>Belkin F6D3000</td>
-    <td>AR5212</td>
-    <td>PCI</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>D-Link DWL-A520</td>
-    <td>AR5210</td>
-    <td>PCI</td>
-    <td>a</td>
-  </tr>
-  <tr>
-    <td>D-Link DWL-A650</td>
-    <td>AR5210</td>
-    <td>CardBus</td>
-    <td>a</td>
-  </tr>
-  <tr>
-    <td>D-Link DWL-AB650</td>
-    <td>AR5211</td>
-    <td>CardBus</td>
-    <td>a/b</td>
-  </tr>
-  <tr>
-    <td>D-Link DWL-AG520</td>
-    <td>AR5212</td>
-    <td>PCI</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>D-Link DWL-AG650</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>D-Link DWL-AG660</td>
-    <td>AR521?</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>D-Link DWL-G520</td>
-    <td>AR5212</td>
-    <td>PCI</td>
-    <td>b/g</td>
-  </tr>
-  <tr>
-    <td>D-Link DWL-G650B</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>b/g</td>
-  </tr>
-  <tr>
-    <td>Elecom LD-WL54</td>
-    <td>AR5211</td>
-    <td>CardBus</td>
-    <td>a</td>
-  </tr>
-  <tr>
-    <td>Elecom LD-WL54AG</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Fujitsu E5454</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Fujitsu E5454</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Fujitsu FMV-JW481</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>HP NC4000</td>
-    <td>AR5212</td>
-    <td>PCI</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>I/O Data WN-A54</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a</td>
-  </tr>
-  <tr>
-    <td>I/O Data WN-AB</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b</td>
-  </tr>
-  <tr>
-    <td>I/O Data WN-AG</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Linksys WMP55AG</td>
-    <td>AR5212</td>
-    <td>PCI</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Linksys WPC51AB</td>
-    <td>AR5211</td>
-    <td>CardBus</td>
-    <td>a/b</td>
-  </tr>
-  <tr>
-    <td>Linksys WPC55AG</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>NEC PA-WL/54AG</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Netgear WAB501</td>
-    <td>AR5211</td>
-    <td>CardBus</td>
-    <td>a/b</td>
-  </tr>
-  <tr>
-    <td>Netgear WAG311</td>
-    <td>AR5212</td>
-    <td>PCI</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Netgear WAG511</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Netgear WG311</td>
-    <td>AR5212</td>
-    <td>PCI</td>
-    <td>b/g</td>
-  </tr>
-  <tr>
-    <td>Netgear WG511T</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>b/g</td>
-  </tr>
-  <tr>
-    <td>Orinoco 8470WD</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Orinoco 8480</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Planex GW-NS54AG</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>Proxim Skyline 4030</td>
-    <td>AR5210</td>
-    <td>CardBus</td>
-    <td>a</td>
-  </tr>
-  <tr>
-    <td>Proxim Skyline 4032</td>
-    <td>AR5210</td>
-    <td>PCI</td>
-    <td>a</td>
-  </tr>
-  <tr>
-    <td>Samsung SWL-5200N</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-  <tr>
-    <td>SMC SMC2735W</td>
-    <td>AR5210</td>
-    <td>CardBus</td>
-    <td>a</td>
-  </tr>
-  <tr>
-    <td>Sony PCWA-C300S</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>b/g</td>
-  </tr>
-  <tr>
-    <td>Sony PCWA-C500</td>
-    <td>AR5210</td>
-    <td>CardBus</td>
-    <td>a</td>
-  </tr>
-  <tr>
-    <td>Sony PCWA-C700</td>
-    <td>AR5212</td>
-    <td>CardBus</td>
-    <td>a/b</td>
-  </tr>
-  <tr>
-    <td>Ubiquiti SRC</td>
-    <td>AR5213</td>
-    <td>CardBus</td>
-    <td>a/b/g</td>
-  </tr>
-</table>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
-<dl class="Bl-diag">
-  <dt>ath%d: unable to attach hardware; HAL status %u</dt>
-  <dd>The Atheros Hardware Access Layer was unable to configure the hardware as
-      requested. The status code is explained in the HAL include file
-      <span class="Pa">contrib/sys/dev/ic/athhal.h</span>.</dd>
-  <dt>ath%d: failed to allocate descriptors: %d</dt>
-  <dd>The driver was unable to allocate contiguous memory for the transmit and
-      receive descriptors. This usually indicates system memory is scarce and/or
-      fragmented.</dd>
-  <dt>ath%d: unable to setup a data xmit queue!</dt>
-  <dd>The request to the HAL to setup the transmit queue for normal data frames
-      failed. This should not happen.</dd>
-  <dt>ath%d: unable to setup a beacon xmit queue!</dt>
-  <dd>The request to the HAL to setup the transmit queue for 802.11 beacon
-      frames failed. This should not happen.</dd>
-  <dt>ath%d: 802.11 address: %s</dt>
-  <dd>The MAC address programmed in the EEPROM is displayed.</dd>
-  <dt>ath%d: hardware error; resetting</dt>
-  <dd>An unrecoverable error in the hardware occurred. Errors of this sort
-      include unrecoverable DMA errors. The driver will reset the hardware and
-      continue.</dd>
-  <dt>ath%d: rx FIFO overrun; resetting</dt>
-  <dd>The receive FIFO in the hardware overflowed before the data could be
-      transferred to the host. This typically occurs because the hardware ran
-      short of receive descriptors and had no place to transfer received data.
-      The driver will reset the hardware and continue.</dd>
-  <dt>ath%d: unable to reset hardware; hal status %u</dt>
-  <dd>The Atheros Hardware Access Layer was unable to reset the hardware as
-      requested. The status code is explained in the HAL include file
-      <span class="Pa">sys/external/isc/atheros_hal/dist/ah.h</span>. This
-      should not happen.</dd>
-  <dt>ath%d: unable to start recv logic</dt>
-  <dd>The driver was unable to restart frame reception. This should not
-    happen.</dd>
-  <dt>ath%d: device timeout</dt>
-  <dd>A frame dispatched to the hardware for transmission did not complete in
-      time. The driver will reset the hardware and continue. This should not
-      happen.</dd>
-  <dt>ath%d: bogus xmit rate 0x%x</dt>
-  <dd>An invalid transmit rate was specified for an outgoing frame. The frame is
-      discarded. This should not happen.</dd>
-  <dt>ath%d: ath_chan_set: unable to reset channel %u (%u MHz)</dt>
-  <dd>The Atheros Hardware Access Layer was unable to reset the hardware when
-      switching channels during scanning. This should not happen.</dd>
-  <dt>ath%d: unable to allocate channel table</dt>
-  <dd>The driver was unable to allocate memory for the table used to hold the
-      set of available channels.</dd>
-  <dt>ath%d: unable to collect channel list from hal</dt>
-  <dd>A problem occurred while querying the HAL to find the set of available
-      channels for the device. This should not happen.</dd>
-  <dt>ath%d: %s: %dM -&gt; %dM (%d ok, %d err, %d retr)</dt>
-  <dd>The driver's rate control algorithm changed the current rate for
-      transmitting frames. This message is temporarily enabled for normal use to
-      help in diagnosing and improving the rate control algorithm. The message
-      indicates the new and old transmit rates and the statistics it used to
-      decide on this change.</dd>
-  <dt>ath%d: failed to enable memory mapping</dt>
-  <dd>The driver was unable to enable memory-mapped I/O to the PCI device
-      registers. This should not happen.</dd>
-  <dt>ath%d: failed to enable bus mastering</dt>
-  <dd>The driver was unable to enable the device as a PCI bus master for doing
-      DMA. This should not happen.</dd>
-  <dt>ath%d: cannot map register space</dt>
-  <dd>The driver was unable to map the device registers into the host address
-      space. This should not happen.</dd>
-  <dt>ath%d: could not map interrupt</dt>
-  <dd>The driver was unable to allocate an IRQ for the device interrupt. This
-      should not happen.</dd>
-  <dt>ath%d: could not establish interrupt</dt>
-  <dd>The driver was unable to install the device interrupt handler. This should
-      not happen.</dd>
-</dl>
-</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">arp(4)</a>, <a class="Xr">cardbus(4)</a>,
-    <a class="Xr">ifmedia(4)</a>, <a class="Xr">netintro(4)</a>,
-    <a class="Xr">pci(4)</a>, <a class="Xr">ifconfig(8)</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">ath</code> device driver first appeared in
-    <span class="Ux">FreeBSD 5.2</span>. It was ported to
-    <span class="Ux">NetBSD 2.0</span>.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1>
-<p class="Pp">The <code class="Nm">ath</code> driver was originally written by
-    <span class="An">Sam Leffler</span>, and was ported to
-    <span class="Ux">NetBSD</span> by <span class="An">David Young</span>.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1>
-<p class="Pp">Different regulatory domains have different default channels for
-    adhoc mode. See <a class="Xr">ifconfig(8)</a> for information on how to
-    change the channel. Different regulatory domains may not be able to
-    communicate with each other with 802.11a as different regulatory domains do
-    not necessarily have overlapping channels.</p>
-<p class="Pp">Revision A1 of the D-LINK DWL-G520 and DWL-G650 are based on an
-    Intersil PrismGT chip and are not supported by this driver.</p>
-<p class="Pp">Revision v2 of the Netgear WG311 is based on a Texas Instruments
-    ACX111 and is not supported by this driver.</p>
-<p class="Pp">Revision v3 of the Netgear WG311 is based on a Marvell Libertas
-    88W8335 and is not supported by this driver.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
-<p class="Pp">Performance in lossy environments is suboptimal. The algorithm
-    used to select the rate for transmitted packets is very simplistic. There is
-    no software retransmit; only hardware retransmit is used. Contributors are
-    encouraged to replace the existing rate control algorithm with a better one
-    (hint: all the information needed is available to the driver).</p>
-<p class="Pp">The driver does not fully enable power-save operation of the chip;
-    consequently power use is suboptimal.</p>
-</section>
-</div>
-<table class="foot">
-  <tr>
-    <td class="foot-date">May 27, 2019</td>
-    <td class="foot-os">NetBSD 10.1</td>
-  </tr>
-</table>