docs: Removed Precompiled HTML

1 files changed, 0 insertions, 165 deletions

diff --git a/static/freebsd/man4/vr.4 3.html b/static/freebsd/man4/vr.4 3.html
deleted file mode 100644
index 3ed5ab38..00000000
--- a/static/freebsd/man4/vr.4 3.html
+++ /dev/null
@@ -1,165 +0,0 @@
-<table class="head">
-  <tr>
-    <td class="head-ltitle">VR(4)</td>
-    <td class="head-vol">Device Drivers Manual</td>
-    <td class="head-rtitle">VR(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">vr</code> &#x2014; <span class="Nd">VIA
-    Technologies Rhine I/II/III Ethernet device driver</span></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
-<p class="Pp">To compile this driver into the kernel, place the following lines
-    in your kernel configuration file:</p>
-<div class="Bd Pp Bd-indent"><code class="Cd">device miibus</code>
-<br/>
-<code class="Cd">device vr</code></div>
-<p class="Pp">Alternatively, to load the driver as a module at boot time, place
-    the following line in <a class="Xr">loader.conf(5)</a>:</p>
-<div class="Bd Pp Bd-indent Li">
-<pre>if_vr_load=&quot;YES&quot;</pre>
-</div>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
-<p class="Pp">The <code class="Nm">vr</code> driver provides support for PCI
-    Ethernet adapters and embedded controllers based on the VIA Technologies
-    VT3043 Rhine I, VT86C100A Rhine II, and VT6105/VT6105M Rhine III Fast
-    Ethernet controller chips.</p>
-<p class="Pp">The VIA Rhine chips use bus master DMA and have a descriptor
-    layout designed to resemble that of the DEC 21x4x &#x201C;tulip&#x201D;
-    chips. The register layout is different however and the receive filter in
-    the Rhine chips is much simpler and is programmed through registers rather
-    than by downloading a special setup frame through the transmit DMA engine.
-    Transmit and receive DMA buffers must be longword aligned. The Rhine chips
-    are meant to be interfaced with external physical layer devices via an MII
-    bus. They support both 10 and 100Mbps speeds in either full or half
-  duplex.</p>
-<p class="Pp">The <code class="Nm">vr</code> driver supports the following media
-    types:</p>
-<dl class="Bl-tag">
-  <dt>autoselect</dt>
-  <dd>Enable autoselection of the media type and options. The user can manually
-      override the autoselected mode by adding media options to the
-      <span class="Pa">/etc/rc.conf</span> file.</dd>
-  <dt>10baseT/UTP</dt>
-  <dd>Set 10Mbps operation. The <var class="Ar">mediaopt</var> option can also
-      be used to select either <var class="Ar">full-duplex</var> or
-      <var class="Ar">half-duplex</var> modes.</dd>
-  <dt>100baseTX</dt>
-  <dd>Set 100Mbps (Fast Ethernet) operation. The <var class="Ar">mediaopt</var>
-      option can also be used to select either <var class="Ar">full-duplex</var>
-      or <var class="Ar">half-duplex</var> modes.</dd>
-</dl>
-<p class="Pp">The <code class="Nm">vr</code> driver supports the following media
-    options:</p>
-<dl class="Bl-tag">
-  <dt>full-duplex</dt>
-  <dd>Force full duplex operation.</dd>
-  <dt>half-duplex</dt>
-  <dd>Force half duplex operation.</dd>
-</dl>
-<p class="Pp">Note that the 100baseTX media type is only available if supported
-    by the adapter. For more information on configuring this device, see
-    <a class="Xr">ifconfig(8)</a>.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="HARDWARE"><a class="permalink" href="#HARDWARE">HARDWARE</a></h1>
-<p class="Pp">The <code class="Nm">vr</code> driver supports VIA Technologies
-    Rhine I, Rhine II, and Rhine III based Fast Ethernet adapters including:</p>
-<p class="Pp"></p>
-<ul class="Bl-bullet Bl-compact">
-  <li>AOpen/Acer ALN-320</li>
-  <li>D-Link DFE520-TX</li>
-  <li>D-Link DFE530-TX</li>
-  <li>Hawking Technologies PN102TX</li>
-  <li>Soekris Engineering net5501</li>
-</ul>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="SYSCTL_VARIABLES"><a class="permalink" href="#SYSCTL_VARIABLES">SYSCTL
-  VARIABLES</a></h1>
-<p class="Pp">The following variables are available as
-    <a class="Xr">sysctl(8)</a> variables:</p>
-<dl class="Bl-tag">
-  <dt id="dev.vr._d.stats"><var class="Va">dev.vr.%d.stats</var></dt>
-  <dd>Display lots of useful MAC counters maintained in the driver.</dd>
-</dl>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
-<dl class="Bl-diag">
-  <dt>vr%d: couldn't map memory</dt>
-  <dd>A fatal initialization error has occurred.</dd>
-  <dt>vr%d: couldn't map interrupt</dt>
-  <dd>A fatal initialization error has occurred.</dd>
-  <dt>vr%d: watchdog timeout</dt>
-  <dd>The device has stopped responding to the network, or there is a problem
-      with the network connection (cable).</dd>
-  <dt>vr%d: no memory for rx list</dt>
-  <dd>The driver failed to allocate an mbuf for the receiver ring.</dd>
-  <dt>vr%d: no memory for tx list</dt>
-  <dd>The driver failed to allocate an mbuf for the transmitter ring when
-      allocating a pad buffer or collapsing an mbuf chain into a cluster.</dd>
-  <dt>vr%d: chip is in D3 power state -- setting to D0</dt>
-  <dd>This message applies only to adapters which support power management. Some
-      operating systems place the controller in low power mode when shutting
-      down, and some PCI BIOSes fail to bring the chip out of this state before
-      configuring it. The controller loses all of its PCI configuration in the
-      D3 state, so if the BIOS does not set it back to full power mode in time,
-      it will not be able to configure it correctly. The driver tries to detect
-      this condition and bring the adapter back to the D0 (full power) state,
-      but this may not be enough to return the driver to a fully operational
-      condition. If you see this message at boot time and the driver fails to
-      attach the device as a network interface, you will have to perform second
-      warm boot to have the device properly configured.
-    <p class="Pp">Note that this condition only occurs when warm booting from
-        another operating system. If you power down your system prior to booting
-        <span class="Ux">FreeBSD</span>, the card should be configured
-        correctly.</p>
-  </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">altq(4)</a>, <a class="Xr">arp(4)</a>,
-    <a class="Xr">miibus(4)</a>, <a class="Xr">netintro(4)</a>,
-    <a class="Xr">ng_ether(4)</a>, <a class="Xr">polling(4)</a>,
-    <a class="Xr">ifconfig(8)</a></p>
-<p class="Pp"><cite class="Rs"><span class="RsT">The VIA Technologies VT86C100A
-    data sheet</span>,
-    <a class="RsU" href="http://www.via.com.tw">http://www.via.com.tw</a>.</cite></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">vr</code> device driver first appeared in
-    <span class="Ux">FreeBSD 3.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">vr</code> driver was written by
-    <span class="An">Bill Paul</span>
-    &lt;<a class="Mt" href="mailto:wpaul@ctr.columbia.edu">wpaul@ctr.columbia.edu</a>&gt;.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
-<p class="Pp">The <code class="Nm">vr</code> driver always copies transmit mbuf
-    chains into longword-aligned buffers prior to transmission in order to
-    pacify the Rhine chips. If buffers are not aligned correctly, the chip will
-    round the supplied buffer address and begin DMAing from the wrong location.
-    This buffer copying impairs transmit performance on slower systems but
-    cannot be avoided. On faster machines (e.g. a Pentium II), the performance
-    impact is much less noticeable.</p>
-</section>
-</div>
-<table class="foot">
-  <tr>
-    <td class="foot-date">February 25, 2012</td>
-    <td class="foot-os">FreeBSD 15.0</td>
-  </tr>
-</table>