docs: Added All NetBSD Manuals

2 files changed, 194 insertions, 0 deletions

diff --git a/static/netbsd/man4/man4.prep/intro.4 3.html b/static/netbsd/man4/man4.prep/intro.4 3.html
new file mode 100644
index 00000000..d17795f2
--- /dev/null
+++ b/static/netbsd/man4/man4.prep/intro.4 3.html
@@ -0,0 +1,105 @@
+<table class="head">
+  <tr>
+    <td class="head-ltitle">INTRO(4)</td>
+    <td class="head-vol">Device Drivers Manual (prep)</td>
+    <td class="head-rtitle">INTRO(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">intro</code> &#x2014;
+    <span class="Nd">introduction to prep special files and hardware
+    support</span></p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
+<p class="Pp">This section describes the special files, related driver
+    functions, and networking support available in the system. In this part of
+    the manual, the SYNOPSIS section of each configurable device gives a sample
+    specification for use in constructing a system description for the
+    <a class="Xr">config(1)</a> program. The DIAGNOSTICS section lists messages
+    which may appear on the console and/or in the system error log
+    <span class="Pa">/var/log/messages</span> due to errors in device operation;
+    see <a class="Xr">syslogd(8)</a> for more information.</p>
+<p class="Pp">This section contains both devices which may be configured into
+    the system and network related information. The networking support is
+    introduced in <a class="Xr">netintro(4)</a>.</p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="PMPPC_DEVICE_SUPPORT"><a class="permalink" href="#PMPPC_DEVICE_SUPPORT">PMPPC
+  DEVICE SUPPORT</a></h1>
+<p class="Pp">This section describes the hardware supported on the PowerPC
+    Reference Platform machines. Software support for these devices comes in two
+    forms. A hardware device may be supported with a character or block
+    <a class="permalink" href="#device"><i class="Em" id="device">device
+    driver</i></a>, or it may be used within the networking subsystem and have a
+    <a class="permalink" href="#network"><i class="Em" id="network">network
+    interface driver</i></a>. Block and character devices are accessed through
+    files in the file system of a special type; see <a class="Xr">mknod(8)</a>.
+    Network interfaces are indirectly accessed through the interprocess
+    communication facilities provided by the system; see
+    <a class="Xr">socket(2)</a>.</p>
+<p class="Pp">A hardware device is identified to the system at configuration
+    time and the appropriate device or network interface driver is then compiled
+    into the system. When the resultant system is booted, the autoconfiguration
+    facilities in the system probe for the device and, if found, enable the
+    software support for it. If a device does not respond at autoconfiguration
+    time it is not accessible at any time afterwards. To enable a device which
+    did not autoconfigure, the system will have to be rebooted.</p>
+<p class="Pp">The autoconfiguration system is described in
+    <a class="Xr">autoconf(4)</a>. A list of the supported devices is given
+    below.</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">config(1)</a>, <a class="Xr">autoconf(4)</a>,
+    <a class="Xr">pnpbus(4)</a>, <a class="Xr">prep/nvram(4)</a></p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
+<p class="Pp">The prep <code class="Nm">intro</code> man page first appeared in
+    <span class="Ux">NetBSD 4.0</span>.</p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="LIST_OF_DEVICES"><a class="permalink" href="#LIST_OF_DEVICES">LIST
+  OF DEVICES</a></h1>
+<p class="Pp">The devices listed below are supported in this incarnation of the
+    system. Devices are indicated by their functional interface. Not all
+    supported devices are listed.</p>
+<p class="Pp">The pnpbus is a pseudo-bus which is a configuration interface for
+    certain devices on PReP machines. These devices are defined in the PReP
+    residual data with configuration information, similar to
+    <a class="Xr">isapnp(4)</a>. The underlying bus is generally ISA.</p>
+<p class="Pp">ISA devices are supported through the <a class="Xr">isa(4)</a> bus
+    and associated devices.</p>
+<p class="Pp">PCI devices are supported through the <a class="Xr">pci(4)</a> bus
+    and associated devices.</p>
+<p class="Pp">USB devices are supported through the <a class="Xr">usb(4)</a> bus
+    and associated devices.</p>
+<p class="Pp">Additionally, the following specific devices are supported:</p>
+<div class="Bd-indent">
+<dl class="Bl-tag Bl-compact">
+  <dt id="com"><a class="permalink" href="#com"><i class="Em">com</i></a></dt>
+  <dd>serial ports</dd>
+  <dt id="nvram"><a class="permalink" href="#nvram"><i class="Em">nvram</i></a></dt>
+  <dd>NVRAM chip</dd>
+  <dt id="wdc"><a class="permalink" href="#wdc"><i class="Em">wdc</i></a></dt>
+  <dd>ISA IDE controller</dd>
+  <dt id="we"><a class="permalink" href="#we"><i class="Em">we</i></a></dt>
+  <dd>Western Digital/SMC WD80x3 ethernet driver</dd>
+  <dt id="mcclock"><a class="permalink" href="#mcclock"><i class="Em">mcclock</i></a></dt>
+  <dd>mc146818 compatible time-of-day clock</dd>
+  <dt id="mkclock"><a class="permalink" href="#mkclock"><i class="Em">mkclock</i></a></dt>
+  <dd>Mostek MK48T18 time-of-day chip</dd>
+</dl>
+</div>
+</section>
+</div>
+<table class="foot">
+  <tr>
+    <td class="foot-date">February 17, 2017</td>
+    <td class="foot-os">NetBSD 10.1</td>
+  </tr>
+</table>
diff --git a/static/netbsd/man4/man4.prep/nvram.4 3.html b/static/netbsd/man4/man4.prep/nvram.4 3.html
new file mode 100644
index 00000000..b4823126
--- /dev/null
+++ b/static/netbsd/man4/man4.prep/nvram.4 3.html
@@ -0,0 +1,89 @@
+<table class="head">
+  <tr>
+    <td class="head-ltitle">NVRAM(4)</td>
+    <td class="head-vol">Device Drivers Manual (prep)</td>
+    <td class="head-rtitle">NVRAM(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">nvram</code> &#x2014; <span class="Nd">PReP nvram
+    interface</span></p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
+<p class="Pp"><code class="In">#include
+    &lt;<a class="In">machine/nvram.h</a>&gt;</code></p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
+<p class="Pp">The file <code class="Nm">/dev/nvram</code> is an interface to the
+    PReP NVRAM, including the Global Environment Area. This interface is highly
+    stylized; ioctls are used for all operations. These ioctls refer to
+    individual variables in the Global Environment Area and their values.</p>
+<p class="Pp">The calls that take and/or return a variable use a pointer to an
+    <code class="Li">int</code> variable for this purpose; others use a pointer
+    to an <code class="Li">struct pnviocdesc</code> descriptor, which contains a
+    variable and two counted strings. The first string comprises the fields
+    <code class="Li">pnv_namelen</code> (an <code class="Li">int</code>) and
+    <code class="Li">pnv_name</code> (a <code class="Li">char *</code>), giving
+    the name of a field. The second string comprises the fields
+    <code class="Li">pnv_buflen</code> and <code class="Li">pnv_buf</code>, used
+    analogously. These two counted strings work in a
+    &#x201C;value-result&#x201D; fashion. At entry to the ioctl, the counts are
+    expected to reflect the buffer size; on return, the counts are updated to
+    reflect the buffer contents.</p>
+<p class="Pp">The following ioctls are supported:</p>
+<dl class="Bl-tag">
+  <dt>PNVIOCGETNEXTNAME</dt>
+  <dd>Takes a variable name and returns the name of the following variable. If a
+      <code class="Dv">NULL</code> is passed as the variable name, the first
+      variable name will be returned. If the last variable is given as an
+      argument, the ioctl will return <code class="Er">EINVAL</code>.</dd>
+  <dt id="PNVIOCGET"><a class="permalink" href="#PNVIOCGET"><code class="Dv">PNVIOCGET</code></a></dt>
+  <dd>Fills in the value of the named property for the given variable. If no
+      such property is associated with that variable, the value length is set to
+      -1. If the named property exists but has no value, the value length is set
+      to 0.</dd>
+  <dt id="PNVIOCSET"><a class="permalink" href="#PNVIOCSET"><code class="Dv">PNVIOCSET</code></a></dt>
+  <dd>Writes the given value under the given name.</dd>
+  <dt id="PNVIOCGETNUMGE"><a class="permalink" href="#PNVIOCGETNUMGE"><code class="Dv">PNVIOCGETNUMGE</code></a></dt>
+  <dd>Returns the number of variables in the Global Environment Area.</dd>
+</dl>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1>
+<p class="Pp"><span class="Pa">/dev/nvram</span></p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="ERRORS"><a class="permalink" href="#ERRORS">ERRORS</a></h1>
+<p class="Pp">The following may result in rejection of an operation:</p>
+<dl class="Bl-tag">
+  <dt id="EINVAL">[<a class="permalink" href="#EINVAL"><code class="Er">EINVAL</code></a>]</dt>
+  <dd>The given variable name does not exist; or the buffer set up to retrieve
+      values from the nvram was not large enough to hold the result.</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">ioctl(2)</a></p>
+<p class="Pp"><span class="Pa">PowerPC Reference Platform Specification Version
+    1.1, Section 5.5</span></p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
+<p class="Pp">Due to limitations within the <code class="Nm">nvram</code>
+    itself, these functions run at elevated priority and may adversely affect
+    system performance.</p>
+<p class="Pp"><code class="Dv">PNVIOCSET</code> is not currently supported,
+    making the <code class="Nm">nvram</code> driver read-only at this time.</p>
+</section>
+</div>
+<table class="foot">
+  <tr>
+    <td class="foot-date">March 1, 2007</td>
+    <td class="foot-os">NetBSD 10.1</td>
+  </tr>
+</table>