docs: Removed Precompiled HTML

1 files changed, 0 insertions, 305 deletions

diff --git a/static/freebsd/man4/mlx.4 3.html b/static/freebsd/man4/mlx.4 3.html
deleted file mode 100644
index a57ecd58..00000000
--- a/static/freebsd/man4/mlx.4 3.html
+++ /dev/null
@@ -1,305 +0,0 @@
-<table class="head">
-  <tr>
-    <td class="head-ltitle">MLX(4)</td>
-    <td class="head-vol">Device Drivers Manual</td>
-    <td class="head-rtitle">MLX(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">mlx</code> &#x2014; <span class="Nd">Mylex
-    DAC-family Parallel SCSI RAID 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 pci</code>
-<br/>
-<code class="Cd">device mlx</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>mlx_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">mlx</code> driver provides support for Mylex
-    DAC-family PCI to SCSI RAID controllers, including versions relabeled by
-    Digital/Compaq.</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">mlx</code> driver supports the following
-    Parallel SCSI RAID controllers:</p>
-<p class="Pp"></p>
-<ul class="Bl-bullet Bl-compact">
-  <li>Mylex DAC960P (Wide Fast SCSI-2)</li>
-  <li>Mylex DAC960PD / DEC KZPSC (Wide Fast SCSI-2)</li>
-  <li>Mylex DAC960PDU (Ultra SCSI-3)</li>
-  <li>Mylex DAC960PL (Wide Fast SCSI-2)</li>
-  <li>Mylex DAC960PJ (Wide Ultra SCSI-3)</li>
-  <li>Mylex DAC960PG (Wide Ultra SCSI-3)</li>
-  <li>Mylex DAC960PU / DEC PZPAC (Wide Ultra SCSI-3)</li>
-  <li>Mylex AcceleRAID 150 (DAC960PRL) (Wide Ultra2 SCSI)</li>
-  <li>Mylex AcceleRAID 250 (DAC960PTL1) (Wide Ultra2 SCSI)</li>
-  <li>Mylex eXtremeRAID 1100 (DAC1164P) (Wide Ultra2 SCSI)</li>
-  <li>RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB
-      cache), KZPAC-CA (3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache)</li>
-</ul>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
-<section class="Ss">
-<h2 class="Ss" id="Controller_initialisation_phase"><a class="permalink" href="#Controller_initialisation_phase">Controller
-  initialisation phase</a></h2>
-<dl class="Bl-diag">
-  <dt>mlx%d: controller initialisation in progress...</dt>
-  <dd></dd>
-  <dt>mlx%d: initialisation complete</dt>
-  <dd>
-    <p class="Pp">The controller firmware is performing/has completed
-        initialisation.</p>
-  </dd>
-  <dt>mlx%d: physical drive %d:%d not responding</dt>
-  <dd>
-    <p class="Pp">The drive at channel:target is not responding; it may have
-        failed or been removed.</p>
-  </dd>
-  <dt>mlx%d: spinning up drives...</dt>
-  <dd>
-    <p class="Pp">Drive startup is in progress; this may take several
-      minutes.</p>
-  </dd>
-  <dt>mlx%d: configuration checksum error</dt>
-  <dd>
-    <p class="Pp">The array configuration has become corrupted.</p>
-  </dd>
-  <dt>mlx%d: mirror race recovery in progress</dt>
-  <dd></dd>
-  <dt>mlx%d: mirror race on a critical system drive</dt>
-  <dd></dd>
-  <dt>mlx%d: mirror race recovery failed</dt>
-  <dd>
-    <p class="Pp">These error codes are undocumented.</p>
-  </dd>
-  <dt>mlx%d: physical drive %d:%d COD mismatch</dt>
-  <dd>
-    <p class="Pp">Configuration data on the drive at channel:target does not
-        match the rest of the array.</p>
-  </dd>
-  <dt>mlx%d: system drive installation aborted</dt>
-  <dd>
-    <p class="Pp">Errors occurred preventing one or more system drives from
-        being configured.</p>
-  </dd>
-  <dt>mlx%d: new controller configuration found</dt>
-  <dd>
-    <p class="Pp">The controller has detected a configuration on disk which
-        supersedes the configuration in its nonvolatile memory. It will reset
-        and come up with the new configuration.</p>
-  </dd>
-  <dt>mlx%d: FATAL MEMORY PARITY ERROR</dt>
-  <dd>
-    <p class="Pp">Firmware detected a fatal memory error; the driver will not
-        attempt to attach to this controller.</p>
-  </dd>
-  <dt>mlx%d: unknown firmware initialisation error %x:%x:%x</dt>
-  <dd>
-    <p class="Pp">An unknown error occurred during initialisation; it will be
-        ignored.</p>
-  </dd>
-</dl>
-</section>
-<section class="Ss">
-<h2 class="Ss" id="Driver_initialisation/shutdown_phase:"><a class="permalink" href="#Driver_initialisation/shutdown_phase:">Driver
-  initialisation/shutdown phase:</a></h2>
-<dl class="Bl-diag">
-  <dt>mlx%d: can't allocate scatter/gather DMA tag</dt>
-  <dd></dd>
-  <dt>mlx%d: can't allocate buffer DMA tag</dt>
-  <dd></dd>
-  <dt>mlx%d: can't allocate s/g table</dt>
-  <dd></dd>
-  <dt>mlx%d: can't make initial s/g list mapping</dt>
-  <dd></dd>
-  <dt>mlx%d: can't make permanent s/g list mapping</dt>
-  <dd></dd>
-  <dt>mlx%d: can't allocate interrupt</dt>
-  <dd></dd>
-  <dt>mlx%d: can't set up interrupt</dt>
-  <dd>
-    <p class="Pp">A resource allocation error occurred while initialising the
-        driver; initialisation has failed and the driver will not attach to this
-        controller.</p>
-  </dd>
-  <dt>mlx%d: error fetching drive status</dt>
-  <dd>
-    <p class="Pp">The current status of all system drives could not be fetched;
-        attachment of system drives will be aborted.</p>
-  </dd>
-  <dt>mlx%d: device_add_child failed</dt>
-  <dd>
-    <p class="Pp">Creation of the system drive instances failed; attachment of
-        one or more system drives may have been aborted.</p>
-  </dd>
-  <dt>mlxd%d: detaching...</dt>
-  <dd>
-    <p class="Pp">The indicated system drive is being detached.</p>
-  </dd>
-  <dt>mlxd%d: still open, can't detach</dt>
-  <dd>
-    <p class="Pp">The indicated system drive is still open or mounted; the
-        controller cannot be detached.</p>
-  </dd>
-  <dt>mlx%d: flushing cache...</dt>
-  <dd>
-    <p class="Pp">The controller cache is being flushed prior to detach or
-        shutdown.</p>
-  </dd>
-</dl>
-</section>
-<section class="Ss">
-<h2 class="Ss" id="Operational_diagnostics:"><a class="permalink" href="#Operational_diagnostics:">Operational
-  diagnostics:</a></h2>
-<dl class="Bl-diag">
-  <dt>mlx%d: ENQUIRY failed - %s</dt>
-  <dd></dd>
-  <dt>mlx%d: ENQUIRY2 failed</dt>
-  <dd></dd>
-  <dt>mlx%d: ENQUIRY_OLD failed</dt>
-  <dd></dd>
-  <dt>mlx%d: FLUSH failed - %s</dt>
-  <dd></dd>
-  <dt>mlx%d: CHECK ASYNC failed - %s</dt>
-  <dd></dd>
-  <dt>mlx%d: REBUILD ASYNC failed - %s</dt>
-  <dd></dd>
-  <dt>mlx%d: command failed - %s</dt>
-  <dd>
-    <p class="Pp">The controller rejected a command for the reason given.</p>
-  </dd>
-  <dt>mlx%d: I/O beyond end of unit (%u,%d &gt; %u)</dt>
-  <dd></dd>
-  <dt>mlx%d: I/O error - %s</dt>
-  <dd>
-    <p class="Pp">An I/O error was reported by the controller.</p>
-  </dd>
-  <dt>mlx%d: periodic enquiry failed - %s</dt>
-  <dd>
-    <p class="Pp">An attempt to poll the controller for status failed for the
-        reason given.</p>
-  </dd>
-  <dt>mlx%d: mlx_periodic_enquiry: unknown command %x</dt>
-  <dd>
-    <p class="Pp">The periodic status poll has issued a command which has become
-        corrupted.</p>
-  </dd>
-  <dt>mlxd%d: drive offline</dt>
-  <dd></dd>
-  <dt>mlxd%d: drive online</dt>
-  <dd></dd>
-  <dt>mlxd%d: drive critical</dt>
-  <dd>
-    <p class="Pp">The system disk indicated has changed state.</p>
-  </dd>
-  <dt>mlx%d: physical drive %d:%d reset</dt>
-  <dd></dd>
-  <dt>mlx%d: physical drive %d:%d killed %s</dt>
-  <dd></dd>
-  <dt>mlx%d: physical drive %d:%d error log: sense = %d asc = %x asq = %x</dt>
-  <dd></dd>
-  <dt>mlx%d: info %4D csi %4D</dt>
-  <dd>
-    <p class="Pp">The drive at channel:target has been reset, killed for the
-        given reason, or experienced a SCSI error.</p>
-  </dd>
-  <dt>mlx%d: unknown log message type %x</dt>
-  <dd></dd>
-  <dt>mlx%d: error reading message log - %s</dt>
-  <dd>
-    <p class="Pp">An error occurred while trying to read the controller's
-        message log.</p>
-  </dd>
-  <dt>mlxd%d: consistency check started</dt>
-  <dd></dd>
-  <dt>mlx%d: consistency check completed</dt>
-  <dd>
-    <p class="Pp">A user-initiated consistency check has started/completed.</p>
-  </dd>
-  <dt>mlx%d: drive rebuild started for %d:%d</dt>
-  <dd></dd>
-  <dt>mlx%d: drive rebuild completed</dt>
-  <dd>
-    <p class="Pp">A user-initiated physical drive rebuild has
-      started/completed.</p>
-  </dd>
-  <dt>mlx%d: background check/rebuild operation started</dt>
-  <dd></dd>
-  <dt>mlx%d: background check/rebuild operation completed</dt>
-  <dd>
-    <p class="Pp">An automatic system drive consistency check or physical drive
-        rebuild has started/completed.</p>
-  </dd>
-  <dt>mlx%d: channel %d pausing for %d seconds</dt>
-  <dd></dd>
-  <dt>mlx%d: channel %d resuming</dt>
-  <dd></dd>
-  <dt>mlx%d: pause command failed - %s</dt>
-  <dd></dd>
-  <dt>mlx%d: pause failed for channel %d</dt>
-  <dd></dd>
-  <dt>mlx%d: resume command failed - %s</dt>
-  <dd></dd>
-  <dt>mlx%d: resume failed for channel %d</dt>
-  <dd>
-    <p class="Pp">Controller/channel pause operation notification. (Channel
-        pause is not currently supported on any controller.)</p>
-  </dd>
-  <dt>mlx%d: controller wedged (not taking commands)</dt>
-  <dd>
-    <p class="Pp">The controller is not responding to attempts to submit new
-        commands.</p>
-  </dd>
-  <dt>mlx%d: duplicate done event for slot %d</dt>
-  <dd></dd>
-  <dt>mlx%d: done event for nonbusy slot %d</dt>
-  <dd>
-    <p class="Pp">Corruption has occurred in either the controller's onboard
-        list of commands or in the driver.</p>
-  </dd>
-</dl>
-</section>
-</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">mlxcontrol(8)</a></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">mlx</code> driver was written by
-    <span class="An">Michael Smith</span>
-    &lt;<a class="Mt" href="mailto:msmith@FreeBSD.org">msmith@FreeBSD.org</a>&gt;.</p>
-<p class="Pp">This manual page was written by <span class="An">Jeroen Ruigrok
-    van der Werven</span>
-    &lt;<a class="Mt" href="mailto:asmodai@FreeBSD.org">asmodai@FreeBSD.org</a>&gt;
-    and <span class="An">Michael Smith</span>
-    &lt;<a class="Mt" href="mailto:msmith@FreeBSD.org">msmith@FreeBSD.org</a>&gt;.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
-<p class="Pp">The DEC KZPSC has insufficient flash ROM to hold any reasonably
-    recent firmware. This has caused problems for this driver.</p>
-<p class="Pp">The driver does not yet support the version 6.x firmware as found
-    in the AcceleRAID 352 and eXtremeRAID 2000 and 3000 products.</p>
-</section>
-</div>
-<table class="foot">
-  <tr>
-    <td class="foot-date">May 27, 2025</td>
-    <td class="foot-os">FreeBSD 15.0</td>
-  </tr>
-</table>