docs: Removed Precompiled HTML

1 files changed, 0 insertions, 74 deletions

diff --git a/static/netbsd/man4/acpiec.4 4.html b/static/netbsd/man4/acpiec.4 4.html
deleted file mode 100644
index d11c6732..00000000
--- a/static/netbsd/man4/acpiec.4 4.html
+++ /dev/null
@@ -1,74 +0,0 @@
-<table class="head">
-  <tr>
-    <td class="head-ltitle">ACPIEC(4)</td>
-    <td class="head-vol">Device Drivers Manual</td>
-    <td class="head-rtitle">ACPIEC(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">acpiec</code> &#x2014; <span class="Nd">ACPI
-    Embedded Controller</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">acpiec* at acpi?</code>
-  <br/>
-  <code class="Cd">acpiecdt* at acpi?</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">acpiec</code> driver supports ACPI Embedded
-    Controllers.</p>
-<p class="Pp">An ACPI Embedded Controller (EC) is typically a small
-    microprocessor that is responsible for various tasks related to ACPI. The
-    primary task is to handle ACPI specific interrupts, which are mapped to
-    so-called ACPI General Purpose Events (GPEs). Other possible functions
-    include embedded access to other buses such as the
-  <a class="Xr">iic(4)</a>.</p>
-<p class="Pp">The ACPI specific events range from user initiated events to
-    events triggered by the hardware. When such an event occurs, typically
-    either a System Management Interrupt (SMI) or a System Control Interrupt
-    (SCI) is raised. The latter is an active, visible, shareable, level
-    interrupt. On most Intel chipsets SCI is hardwired to the interrupt number
-    9. The main task of an EC is to raise a system control interrupt.</p>
-<p class="Pp">All GPEs generate SCIs. A typical example of the internal wiring
-    of GPEs could involve <a class="Xr">gpio(4)</a>: when, e.g., the AC adapter
-    is connected, a certain GPIO line becomes active, a given GPE is flagged,
-    and a SCI interrupt is raised by the EC, leading to execution of ACPI
-    machine code in order to locate the handler associated with the event. A
-    corresponding driver, <a class="Xr">acpiacad(4)</a> in this case, will
-    finally finish the processing of the event.</p>
-<p class="Pp">Due to the reasons described above, majority of ACPI specific
-    drivers are dysfunctional without <code class="Nm">acpiec</code>. It is
-    therefore recommended that <code class="Nm">acpiec</code> is always enabled,
-    even though it may not be required on some older systems.</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">acpi(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">acpiec</code> driver appeared in
-    <span class="Ux">NetBSD 1.6</span>.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1>
-<p class="Pp">Many machines depend on early attachment of
-    <code class="Nm">acpiec</code>. In such cases the information required by
-    <code class="Nm">acpiec</code> should be available as a separate and
-    optional Embedded Controller Descriptor Table (ECDT). If an ECDT is not
-    available or early attachment can not be carried out due other reasons, the
-    initialization of the whole <a class="Xr">acpi(4)</a> subsystem may be
-    problematic.</p>
-</section>
-</div>
-<table class="foot">
-  <tr>
-    <td class="foot-date">February 27, 2010</td>
-    <td class="foot-os">NetBSD 10.1</td>
-  </tr>
-</table>