diff options
Diffstat (limited to 'static/netbsd/man4/man4.x86')
22 files changed, 0 insertions, 1598 deletions
diff --git a/static/netbsd/man4/man4.x86/amdccp.4 4.html b/static/netbsd/man4/man4.x86/amdccp.4 4.html deleted file mode 100644 index f23eac6b..00000000 --- a/static/netbsd/man4/man4.x86/amdccp.4 4.html +++ /dev/null @@ -1,44 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">AMDCCP(4)</td> - <td class="head-vol">Device Drivers Manual</td> - <td class="head-rtitle">AMDCCP(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">amdccp</code> — <span class="Nd">AMD - Cryptographic Coprocessor device 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">amdccp* at pci?</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">amdccp</code> driver provides support for - cryptographic coprocessors found on certain AMD CPUs. The coprocessor - supports hardware offloading for common cryptographic algorithms and a True - Random Number Generator (TRNG).</p> -<p class="Pp">Currently, this driver only supports providing additional entropy - to the kernel's random number generator.</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">pci(4)</a>, <a class="Xr">rnd(4)</a>, - <a class="Xr">entropy(7)</a>, <a class="Xr">rnd(9)</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">amdccp</code> device driver appeared in - <span class="Ux">NetBSD 9.0</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">July 25, 2021</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/amdpcib.4 4.html b/static/netbsd/man4/man4.x86/amdpcib.4 4.html deleted file mode 100644 index 19656ccd..00000000 --- a/static/netbsd/man4/man4.x86/amdpcib.4 4.html +++ /dev/null @@ -1,55 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">AMDPCIB(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">AMDPCIB(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">amdpcib</code> — <span class="Nd">AMD-8111 - series LPC bridge and timecounter</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">amdpcib* at pci?</code> - <br/> - <code class="Cd">hpet* at amdpcib?</code> - <br/> - <code class="Cd">isa* at amdpcib?</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">amdpcib</code> driver provides support for - the AMD-8111 LPC bridge and implements a 32/64-bit 14.3 MHz (or variable) - timecounter using the HPET timer.</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">isa(4)</a>, <a class="Xr">pci(4)</a>, - <a class="Xr">x86/hpet(4)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Advanced Micro Devices</span>, - <span class="RsT">AMD-8111 HyperTransport I/O Hub</span>, - <span class="RsN">Revision 3.03</span>, - <a class="RsU" href="http://support.amd.com/us/ChipsetMotherboard_TechDocs/24674.pdf">http://support.amd.com/us/ChipsetMotherboard_TechDocs/24674.pdf</a>, - <span class="RsD">July, 2004</span>.</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">amdpcib</code> driver first appeared in - <span class="Ux">NetBSD 5.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp"><span class="An">Nicolas Joly</span> - ⟨njoly@NetBSD.org⟩</p> -</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.x86/amdsmn.4 4.html b/static/netbsd/man4/man4.x86/amdsmn.4 4.html deleted file mode 100644 index 640e5f38..00000000 --- a/static/netbsd/man4/man4.x86/amdsmn.4 4.html +++ /dev/null @@ -1,46 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">AMDSMN(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">AMDSMN(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">amdsmn</code> — <span class="Nd">device - driver for AMD processor System Management Network</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">amdsmn* at pci?</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">amdsmn</code> driver provides support for - resources on the System Management Network bus in AMD Family 19h processors, - 17h processors and some later AMD Family 15h processors.</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">amdzentemp(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">amdsmn</code> driver first appeared in - <span class="Ux">FreeBSD</span> and <span class="Ux">NetBSD 9.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp">Based on the <span class="Ux">FreeBSD</span> driver by - <span class="An">Conrad Meyer</span>. It was adapted to - <span class="Ux">NetBSD</span> by <span class="An">Ian Clark</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">October 2, 2022</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/amdzentemp.4 4.html b/static/netbsd/man4/man4.x86/amdzentemp.4 4.html deleted file mode 100644 index 0d564ab2..00000000 --- a/static/netbsd/man4/man4.x86/amdzentemp.4 4.html +++ /dev/null @@ -1,82 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">AMDZENTEMP(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">AMDZENTEMP(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">amdzentemp</code> — <span class="Nd">AMD - Zen CPU family on-die digital thermal sensor</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">amdzentemp* at amdsmnbus?</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">amdzentemp</code> driver provides support for - the on-die digital thermal sensor present on AMD Ryzen CPUs and some later - AMD Opteron CPUs.</p> -<p class="Pp">These sensors provide 0.125°C accuracy. There is one sensor - for each CPU socket.</p> -<p class="Pp">The <code class="Nm">amdzentemp</code> driver reports temperatures - through the <a class="Xr">envsys(4)</a> API.</p> -<table class="Bl-column Bd-indent"> - <tr id="Sensor"> - <td><a class="permalink" href="#Sensor"><b class="Sy">Sensor</b></a></td> - <td><a class="permalink" href="#Units"><b class="Sy" id="Units">Units</b></a></td> - <td><a class="permalink" href="#Typical"><b class="Sy" id="Typical">Typical - Use</b></a></td> - </tr> - <tr> - <td>CPU<i class="Em">N</i> <span class="No">sensor0</span></td> - <td>μK</td> - <td>cpu<i class="Em">N</i> <span class="No">temperature</span></td> - </tr> -</table> -</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">amdtemp(4)</a>, <a class="Xr">envsys(4)</a>, - <a class="Xr">envstat(8)</a>, <a class="Xr">powerd(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">amdzentemp</code> driver first appeared in - <span class="Ux">OpenBSD 4.4</span> named “kate”. It was then - ported to <span class="Ux">NetBSD 5.0</span> under the name - <a class="Xr">amdtemp(4)</a>. The <span class="Ux">FreeBSD</span> version of - the driver was updated with support for newer AMD CPUs. For - <span class="Ux">NetBSD</span>, the support for the newer CPUs was separated - into its own <code class="Nm">amdzentemp</code> driver.</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">amdzentemp</code> driver was written by - <span class="An">Constantine A. Murenin</span> - <<a class="Mt" href="mailto:cnst@openbsd.org">cnst@openbsd.org</a>> - whilst at the University of Waterloo. Porting of support for the newer AMD - CPUs from <span class="Ux">FreeBSD</span> was provided by - <span class="An">Ian Clark</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The temperature reading provided to <a class="Xr">envsys(4)</a> - needs to have a CPU-dependent offset applied. For Ryzen X processors, the - offset is 20°C, while for Threadripper processors an offset of - 27°C is needed.</p> -<p class="Pp">The sensor has a thermal-trip value which should be retrieved and - provided to <a class="Xr">envsys(4)</a> as the sensors critical-maximum - value.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 20, 2020</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/apic.4 4.html b/static/netbsd/man4/man4.x86/apic.4 4.html deleted file mode 100644 index 39537493..00000000 --- a/static/netbsd/man4/man4.x86/apic.4 4.html +++ /dev/null @@ -1,101 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">APIC(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">APIC(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">apic</code>, <code class="Nm">ioapic</code>, - <code class="Nm">lapic</code> — <span class="Nd">Intel APIC - Architecture</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">ioapic* at mainbus*</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">apic</code> subsystem provides basis for a - system of advanced programmable interrupt controllers (APICs) originally - designed by Intel but now widely used on all x86 systems.</p> -<p class="Pp">There are two elements in the architecture, the local APIC (LAPIC) - and the I/O APIC. Historically these were connected by a dedicated 3-wire - “APIC bus”, but the system bus is used for communication - today. The configuration is increasingly dependent on ACPI.</p> -<p class="Pp">Typically each CPU in the system contains one LAPIC that performs - two primary functions:</p> -<ol class="Bl-enum Bd-indent"> - <li>It receives interrupts both from internal sources and from the external - I/O APIC. The interrupt sources include I/O devices, the programmable APIC - timer, performance monitoring counters, thermal sensor interrupts, and - others.</li> - <li>In multiprocessor (MP) systems a LAPIC receives and sends interprocessor - interrupts (IPIs) from and to other processors in the system. IPIs are - used to provide software interrupts, interrupt forwarding, or preemptive - scheduling. Against this, the architecture can be generally seen as an - attempt to solve the interrupt routing efficiency issues in MP - systems.</li> -</ol> -<p class="Pp">There is typically one I/O APIC for each peripheral bus in the - system. Each I/O APIC has a series of interrupt inputs to external interrupt - sources. The architecture usually contains a redirection table which can be - used to route the interrupts that an I/O APIC receives to one or more local - APICs. When a LAPIC is able to accept an interrupt, it will signal the CPU. - Without an I/O APIC, the local APICs are therefore mostly useless; one of - the primary functions of the architecture is no longer achievable, - interrupts can not be distributed to different CPUs.</p> -<p class="Pp">The 8259 PIC has coexisted with the architecture since its - introduction. It is still possible to disable the APIC system and revert - back to a 8259-compatible PIC. But the widespread use of MP systems has made - this mainly a fallback option.</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>, <a class="Xr">mainbus(4)</a>, - <a class="Xr">x86/ichlpcib(4)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Intel 64 and IA-32 Architectures Software Developer's - Manual</span>, <span class="RsV">Volume 3A: System Programming Guide, Part - 1</span>, - <a class="RsU" href="http://www.intel.com/Assets/PDF/manual/253668.pdf">http://www.intel.com/Assets/PDF/manual/253668.pdf</a>, - <span class="RsP">Chapter 10</span>, <span class="RsD">January, - 2011</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Intel 82093AA I/O Advanced Programmable</span>, - <span class="RsT">Interrupt Controller (I/O APIC) Datasheet</span>, - <a class="RsU" href="http://www.intel.com/design/chipsets/datashts/29056601.pdf">http://www.intel.com/design/chipsets/datashts/29056601.pdf</a>, - <span class="RsD">May, 1996</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">8259A, Programmable Interrupt Controller</span>, - <a class="RsU" href="http://pdos.csail.mit.edu/6.828/2005/readings/hardware/8259A.pdf">http://pdos.csail.mit.edu/6.828/2005/readings/hardware/8259A.pdf</a>, - <span class="RsD">December, 1988</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsA">John Baldwin</span>, - <span class="RsT">PCI Interrupts for x86 Machines under FreeBSD</span>, - <a class="RsU" href="http://people.freebsd.org/~jhb/papers/bsdcan/2007/article.pdf">http://people.freebsd.org/~jhb/papers/bsdcan/2007/article.pdf</a>, - <span class="RsD">May 18-19, 2007</span>, <span class="RsO">Proceedings of - BSDCan 2007</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Microsoft Corporation</span>, - <span class="RsT">PCI IRQ Routing on a Multiprocessor ACPI System</span>, - <a class="RsU" href="http://www.microsoft.com/whdc/archive/acpi-mp.mspx">http://www.microsoft.com/whdc/archive/acpi-mp.mspx</a>, - <span class="RsD">December 4, 2001</span>.</cite></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp">Authors of the <span class="Ux">NetBSD</span> implementation of - the Intel APIC Architecture include <span class="An">Andrew Doran</span>, - <span class="An">Bill Sommerfeld</span>, <span class="An">Frank van der - Linden</span>, and <span class="An">Stefan Grefen</span>, among others. The - older 8259 PIC implementation is based on the work of - <span class="An">William Jolitz</span>.</p> -</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.x86/autoconf.4 4.html b/static/netbsd/man4/man4.x86/autoconf.4 4.html deleted file mode 100644 index c2ab14db..00000000 --- a/static/netbsd/man4/man4.x86/autoconf.4 4.html +++ /dev/null @@ -1,45 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">AUTOCONF(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">AUTOCONF(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">autoconf</code> — - <span class="Nd">diagnostics from the autoconfiguration code</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">When <span class="Ux">NetBSD</span> bootstraps it probes the - innards of the machine on which it is running and locates controllers, - drives, and other devices, printing out what it finds on the console. This - procedure is driven by a system configuration table which is processed by - <a class="Xr">config(1)</a> and compiled into each kernel. Devices which - exist in the machine but are not configured into the kernel are not - detected.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<dl class="Bl-diag"> - <dt>CPU class not configured.</dt> - <dd>You tried to boot <span class="Ux">NetBSD</span> on a class of CPU type - which it doesn't (or at least this compiled version of - <span class="Ux">NetBSD</span> doesn't) understand.</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">config(1)</a>, <a class="Xr">intro(4)</a>, - <a class="Xr">boot(8)</a></p> -</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.x86/balloon.4 4.html b/static/netbsd/man4/man4.x86/balloon.4 4.html deleted file mode 100644 index 068c9029..00000000 --- a/static/netbsd/man4/man4.x86/balloon.4 4.html +++ /dev/null @@ -1,159 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BALLOON(4)</td> - <td class="head-vol">Device Drivers Manual (xen)</td> - <td class="head-rtitle">BALLOON(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">balloon</code> — <span class="Nd">Xen - memory balloon 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">balloon* at xenbus?</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">balloon</code> driver supports the memory - ballooning operations offered in Xen environments. It allows shrinking or - extending a domain's available memory by passing pages between different - domains. At any time, the total memory available to a domain is called the - ``reservation''.</p> -<p class="Pp">Pages are moved via the use of the balloon, a reserved quantity of - memory available to all domains that can be freely deflated (or inflated) at - a domain's will. Deflating balloon means that pages are moved out from it, - and bound to domain's virtual memory. Respectively, inflating balloon - indicates that pages are moved out of domain's memory and pushed inside - balloon. This is similar to a dynamic allocation of wired physical memory, - except that the pages are not available to domain anymore.</p> -<p class="Pp">Any domain is free to request memory from - <code class="Nm">balloon</code> up to the maximum value set by the host's - administrator through the <code class="Ic">mem-max</code> command of - <a class="Xr">xm(1)</a>. Alternatively, the host's administrator is free to - request to a particular domain to give some memory back. This command - requires the targeted domain's cooperation and requires - <code class="Nm">balloon</code> support within it. This can be done through - the <code class="Ic">mem-set</code> command of <a class="Xr">xm(1)</a>. - Alternatively, one can control the ballooning directly by writing under the - “memory/target” node inside Xenstore. This entry controls the - target memory reservation of a given domain, indicated in kilobytes - (KiB).</p> -<p class="Pp">An interface to control <code class="Nm">balloon</code> is also - available through <a class="Xr">sysctl(8)</a> under - “machdep.xen.balloon” (all values being in kilobytes):</p> -<dl class="Bl-tag"> - <dt>current</dt> - <dd>(read-only) The current memory reservation of the domain.</dd> - <dt>min</dt> - <dd>(read-write) The minimum reservation value acceptable by the domain's - <code class="Nm">balloon</code> driver. Any request that would require - domain to reduce its reservation below this threshold will be refused by - the driver. This can be used by a domain's administrator to control the - number of memory pages that will be kept available to domain.</dd> - <dt>max</dt> - <dd>(read-only) The maximum reservation accessible to a domain. Its value can - only be changed by the dom0's administrator, through the - <code class="Ic">mem-max</code> command of <a class="Xr">xm(1)</a>.</dd> - <dt>target</dt> - <dd>(read-write) The target reservation of the domain. This entry serves the - same purpose as the “memory/target” entry in Xenstore. This - controls the targeted number of pages that the domain should have. Note - that this is only a target, and may not be achieved for a variety of - reasons.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<dl class="Bl-diag"> - <dt>WARNING: balloon could not reach target %zu (current %zu)</dt> - <dd><code class="Nm">balloon</code> failed to reach the target reservation. - This is typically due to a target set too low; the kernel prevented memory - exhaustion by refusing further allocation.</dd> - <dt>increase reservation incomplete: was %zu, returned %d</dt> - <dd>The hypervisor only gave a partial set of memory pages to domain. This - happens when host's memory consumption is high, and hypervisor is unable - to give enough free pages back to domain.</dd> - <dt>memory 'hot-plug' unsupported - clipping reservation %zu => %zu - pages.</dt> - <dd>An attempt was made by domain to get more memory than initially obtained - during boot. As physical memory pages cannot be added to memory management - sub-system dynamically, <code class="Nm">balloon</code> will limit - reservation up to the maximum value it can handle.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="ERRORS"><a class="permalink" href="#ERRORS">ERRORS</a></h1> -<p class="Pp">When setting the minimum threshold or target reservation entries - through “machdep.xen.balloon”, the following errors can be - returned:</p> -<dl class="Bl-tag"> - <dt id="EPERM">[<a class="permalink" href="#EPERM"><code class="Er">EPERM</code></a>]</dt> - <dd>The value passed is beyond limits. The new value is either too low - (“min” is below driver's safeguard value, or - “target” is below minimum value), or too high - (“target” is above maximum value).</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">xm(1)</a>, <a class="Xr">xenbus(4)</a>, - <a class="Xr">uvm(9)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Carl A. Waldspurger</span>, - <span class="RsT">Memory Resource Management in VMware ESX Server</span>, - <i class="RsB">Proceedings of the 5th Symposium on Operating Systems Design - and Implementation</i>, <i class="RsI">USENIX Association</i>, - <a class="RsU" href="http://www.usenix.org/events/osdi02/tech/full_papers/waldspurger/waldspurger.pdf">http://www.usenix.org/events/osdi02/tech/full_papers/waldspurger/waldspurger.pdf</a>, - <span class="RsD">December 9-11, 2002</span>.</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">balloon</code> driver first appeared in - <span class="Ux">NetBSD 6.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">balloon</code> driver was written by - <span class="An">Cherry G. Mathew</span> - <<a class="Mt" href="mailto:cherry@NetBSD.org">cherry@NetBSD.org</a>> - and <span class="An">Jean-Yves Migeon</span> - <<a class="Mt" href="mailto:jym@NetBSD.org">jym@NetBSD.org</a>>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">There are a number of reasons why a domain may not attain the - targeted memory reservation: <code class="Nm">balloon</code> can be empty - and cannot be collapsed further, domain may not have enough free memory - pages (due to memory fragmentation, memory exhaustion, ...) so it cannot - give enough back to <code class="Nm">balloon</code>.</p> -<p class="Pp">Currently, the virtual memory sub-system of - <span class="Ux">NetBSD</span> is not capable of ``hot-plugging'' new memory - pages into place. This means that increasing a domain's memory reservation - above its initial maximum value is pointless, as new memory pages cannot be - consumed by the memory management sub-system.</p> -<p class="Pp">Over expanding <code class="Nm">balloon</code> generates high - kernel memory pressure. While the driver tries to stay as conservative as - possible to avoid crashes, a very low memory reservation will lead to - unwanted swap or even <code class="Fn">panic</code>().</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SECURITY_CONSIDERATIONS"><a class="permalink" href="#SECURITY_CONSIDERATIONS">SECURITY - CONSIDERATIONS</a></h1> -<p class="Pp">Ballooning involves moving pages between different domains. This - includes their content, which can lead to information leak. If you are - running domains of different sensitivities on the same host, consider - disabling the use of ballooning altogether. The - <span class="Ux">NetBSD</span> kernel zeroes all pages before relinquishing - them to <code class="Nm">balloon</code> but this may not be the case for - other operating systems.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">July 30, 2011</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/console.4 3.html b/static/netbsd/man4/man4.x86/console.4 3.html deleted file mode 100644 index d5718dfc..00000000 --- a/static/netbsd/man4/man4.x86/console.4 3.html +++ /dev/null @@ -1,114 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">CONS(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">CONS(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">console</code> — <span class="Nd">x86 - console 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="Cd">options CONSDEVNAME=string</code> - <br/> - <code class="Cd">options CONADDR=integer</code> - <br/> - <code class="Cd">options CONSPEED=integer</code> - <br/> - <code class="Cd">options CONS_OVERRIDE</code> - <br/> - <code class="Cd">options CONMODE=integer</code></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The “console” device is used for - <i class="Em">kernel printf</i> messages and accesses to the - <span class="Pa">/dev/console</span> character special device in user mode. - It is attached to a hardware interface at boot time controlled by options in - the kernel configuration file, or information passed by the boot loader.</p> -<p class="Pp">Bootblocks from <span class="Ux">NetBSD 1.4</span> or newer select - their console device from a compiled-in list, and then pass their choice of - console device and console parameters to the kernel.</p> -<p class="Pp">As of <span class="Ux">NetBSD 1.5</span>, the - <code class="Ic">consdev</code> bootblock command allows changing the - console device on-the-fly.</p> -<p class="Pp">The kernel will use the same console device as the bootblock; no - special kernel configuration is required.</p> -<p class="Pp">To override the bootblock's choice of console, or to use a serial - kernel console with older bootblocks, you must specify kernel config-file - options to override the information passed by the bootblock. The current - option choices are:</p> -<dl class="Bl-tag"> - <dt>- the standard PC keyboard and display</dt> - <dd>(with either the “pc” or the <a class="Xr">wscons(4)</a> - driver)</dd> - <dt>- standard PC serial ports</dt> - <dd>(with <a class="Xr">com(4)</a> driver)</dd> -</dl> -<p class="Pp">The available <i class="Em">kernel configuration</i> options - are:</p> -<dl class="Bl-ohang"> - <dt><code class="Cd">options CONSDEVNAME=string</code></dt> - <dd>specifies the name of the console device. Valid values are - “pc” for the pc keyboard / display (default) and - “com” for a serial port.</dd> - <dt><code class="Cd">options CONADDR=integer</code></dt> - <dd>sets the base address for the serial console port (default: 0x3f8).</dd> - <dt><code class="Cd">options CONSPEED=integer</code></dt> - <dd>sets the baudrate for the serial console (default: 9600).</dd> - <dt><code class="Cd">options CONS_OVERRIDE</code></dt> - <dd>causes console information passed by the bootloader to be ignored and the - settings specified by the three options above (or the defaults) to be - used. Default behaviour is to use the settings from the bootloader if - present, and to use option / default values only if no information was - passed.</dd> - <dt id="CS8"><code class="Cd">options CONMODE=integer</code></dt> - <dd>allows to specify terminal control flags. The argument is a - “cflag” value, see <a class="Xr">termios(4)</a> for details. - Default is (<code class="Li">CREAD</code> | - <a class="permalink" href="#CS8"><code class="Li">CS8</code></a> | - <a class="permalink" href="#HUPCL"><code class="Li" id="HUPCL">HUPCL</code></a>) - (8N1). This option takes always effect, because mode settings are not - passed by the bootloader.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1> -<dl class="Bl-tag"> - <dt><span class="Pa">/dev/console</span></dt> - <dd style="width: auto;"> </dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> -<p class="Pp"><code class="Cd">options - CONSDEVNAME="\"com\"",CONADDR=0x2f8,CONSPEED=57600</code></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">tty(4)</a>, - <a class="Xr">boot(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The console device is chosen early in system startup regardless if - the specified driver / device is present in the system configuration file. - If the driver asked for by the bootloader or - “<code class="Cd">options CONSDEVNAME</code>” is not - configured into the system, a panic is caused. Because there is no console - device, no explaining message will be printed. If the driver is present, but - the specific device instance not, kernel printf will work, but - <span class="Pa">/dev/console</span> becomes a dummy.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">September 6, 2006</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/coretemp.4 4.html b/static/netbsd/man4/man4.x86/coretemp.4 4.html deleted file mode 100644 index bbbd0f3c..00000000 --- a/static/netbsd/man4/man4.x86/coretemp.4 4.html +++ /dev/null @@ -1,66 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">CORETEMP(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">CORETEMP(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">coretemp</code> — <span class="Nd">Intel - Core on-die digital thermal sensor</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">coretemp* at cpu?</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">coretemp</code> driver provides support for - the on-die digital thermal sensor present on Intel Core and newer CPUs.</p> -<p class="Pp">The temperatures can be observed by using the - <a class="Xr">envsys(4)</a> API or the <a class="Xr">envstat(8)</a> command. - Temperatures are reported for each core separately.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="EVENTS"><a class="permalink" href="#EVENTS">EVENTS</a></h1> -<p class="Pp">The <code class="Nm">coretemp</code> driver is able to send a - <a class="permalink" href="#critical"><i class="Em" id="critical">critical</i></a> - event to the <a class="Xr">powerd(8)</a> daemon. The script - <span class="Pa">/etc/powerd/scripts/sensor_temperature</span> will be - executed by the daemon (if running) when the limit has been reached.</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">envsys(4)</a>, <a class="Xr">envstat(8)</a>, - <a class="Xr">powerd(8)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Michael Berktold</span> and - <span class="RsA">Tian Tian (Intel Corporation)</span>, - <span class="RsT">CPU Monitoring With DTS/PECI, White Paper</span>, - <a class="RsU" href="http://edc.intel.com/Download.aspx?id=2612">http://edc.intel.com/Download.aspx?id=2612</a>, - <span class="RsD">September 2010</span>.</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">coretemp</code> driver first appeared in - <span class="Ux">FreeBSD 7.0</span>. It was later ported to - <span class="Ux">NetBSD 5.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">coretemp</code> driver was written by - <span class="An">Rui Paulo</span> - <<a class="Mt" href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>> - as part of a Google Summer of Code project. It was adapted to - <span class="Ux">NetBSD</span> by <span class="An">Juan Romero - Pardines</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 23, 2010</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/est.4 4.html b/static/netbsd/man4/man4.x86/est.4 4.html deleted file mode 100644 index 5b78affd..00000000 --- a/static/netbsd/man4/man4.x86/est.4 4.html +++ /dev/null @@ -1,68 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">EST(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">EST(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">est</code> — <span class="Nd">Enhanced - SpeedStep</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">est0 at cpu0</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">est</code> driver provides support for - Enhanced SpeedStep introduced in Intel's first and second generation of - Pentium M processors. The following <a class="Xr">sysctl(8)</a> variables - are available with <code class="Nm">est</code>:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="machdep.cpu.frequency.target"><a class="permalink" href="#machdep.cpu.frequency.target"><code class="Ic">machdep.cpu.frequency.target</code></a></dt> - <dd>The target frequency of the CPUs.</dd> - <dt id="machdep.cpu.frequency.current"><a class="permalink" href="#machdep.cpu.frequency.current"><code class="Ic">machdep.cpu.frequency.current</code></a></dt> - <dd>The current frequency.</dd> - <dt id="machdep.cpu.frequency.available"><a class="permalink" href="#machdep.cpu.frequency.available"><code class="Ic">machdep.cpu.frequency.available</code></a></dt> - <dd>The frequencies recognized by <code class="Nm">est</code>.</dd> -</dl> -</div> -<p class="Pp">Note, however, that these variables are not guaranteed to exist in - the future versions of <span class="Ux">NetBSD</span>.</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">acpicpu(4)</a>, <a class="Xr">x86/odcm(4)</a>, - <a class="Xr">x86/powernow(4)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Intel Pentium M Processor.</span>, - <span class="RsT">Datasheet</span>, - <a class="RsU" href="http://download.intel.com/support/processors/mobile/pm/sb/25261203.pdf">http://download.intel.com/support/processors/mobile/pm/sb/25261203.pdf</a>, - <span class="RsD">March, 2004</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Enhanced Intel SpeedStep Technology for the Intel Pentium - M Processor.</span>, <span class="RsT">White Paper</span>, - <a class="RsU" href="http://download.intel.com/design/network/papers/30117401.pdf">http://download.intel.com/design/network/papers/30117401.pdf</a>, - <span class="RsD">March, 2004</span>.</cite></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1> -<p class="Pp">The <code class="Nm">est</code> driver is considered a legacy - interface to be used only with old systems. It is known to be problematic - with new CPUs. Furthermore, in the unlikely case where both - <code class="Nm">est</code> and <a class="Xr">x86/ichlpcib(4)</a> or - <a class="Xr">piixpcib(4)</a> provide support for SpeedStep, the PCI-based - interfaces should not be accessed due possible race conditions.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">September 7, 2020</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/fdc.4 4.html b/static/netbsd/man4/man4.x86/fdc.4 4.html deleted file mode 100644 index 73fd66fb..00000000 --- a/static/netbsd/man4/man4.x86/fdc.4 4.html +++ /dev/null @@ -1,110 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">FDC(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">FDC(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">fdc</code> — <span class="Nd">NEC 765 - floppy disk controller 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">fdc0 at isa? port 0x3f0 irq 6 drq 2</code> - <br/> - <code class="Cd">fdc* at acpi?</code> - <br/> - <code class="Cd">fdc* at pnpbios? index ?</code> - <br/> - <code class="Cd">fd* at fdc? drive ?</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">fdc</code> driver provides support for the - NEC 765 floppy disk controller and floppy disk drives, commonly found on - IBM-PC compatible systems.</p> -<p class="Pp">The driver supports the following floppy diskette formats by using - particular partitions:</p> -<div class="Bd-indent"> -<dl class="Bl-tag Bl-compact"> - <dt>1.44MB 3.5-inch (b)</dt> - <dd style="width: auto;"> </dd> - <dt>1.2MB 5.25-inch (c)</dt> - <dd style="width: auto;"> </dd> - <dt>360KB 5.25-inch (1.2MB drive) (d)</dt> - <dd style="width: auto;"> </dd> - <dt>360KB 5.25-inch (IBM-PC drive) (e)</dt> - <dd style="width: auto;"> </dd> - <dt>720KB 3.5-inch (f)</dt> - <dd style="width: auto;"> </dd> - <dt>720KB 5.25-inch (g)</dt> - <dd style="width: auto;"> </dd> - <dt>360KB 3.5-inch (h)</dt> - <dd style="width: auto;"> </dd> -</dl> -</div> -Partition <var class="Ar">a</var> selects the default format for the attached - floppy drive, as determined by the BIOS configuration for the diskette drive. -</section> -<section class="Sh"> -<h1 class="Sh" id="FORMATTING"><a class="permalink" href="#FORMATTING">FORMATTING</a></h1> -<p class="Pp">The driver supports floppy disk formatting using the interfaces in - <code class="In"><<a class="In">sys/fdio.h</a>></code>:</p> -<dl class="Bl-tag Bl-compact"> - <dt id="FDIOCGETFORMAT"><a class="permalink" href="#FDIOCGETFORMAT"><code class="Dv">FDIOCGETFORMAT</code></a> - <var class="Fa">struct fdformat_parms</var></dt> - <dd>Fetch current formatting parameters. This gets the default parameters for - the open device if no parameters have been set during the session.</dd> - <dt id="FDIOCSETFORMAT"><a class="permalink" href="#FDIOCSETFORMAT"><code class="Dv">FDIOCSETFORMAT</code></a> - <var class="Fa">struct fdformat_parms</var></dt> - <dd>Set formatting parameters. The driver saves this state and it persists - while the device is open.</dd> - <dt id="FDIOCFORMAT_TRACK"><a class="permalink" href="#FDIOCFORMAT_TRACK"><code class="Dv">FDIOCFORMAT_TRACK</code></a> - <var class="Fa">struct fdformat_cmd</var></dt> - <dd>Format a track on the medium. If this call returns - <code class="Er">EINVAL</code>, the track formatting parameters were out - of range for the medium. If it returns <code class="Er">EIO</code>, there - was a medium error while formatting the track.</dd> - <dt id="FDIOCSETOPTS"><a class="permalink" href="#FDIOCSETOPTS"><code class="Dv">FDIOCSETOPTS</code></a> - <var class="Fa">int</var></dt> - <dd>Set driver options which persist until the device is closed. The options - should be the logical OR of the desired values below: - <dl class="Bl-tag Bl-compact"> - <dt id="FDOPT_NORETRY"><a class="permalink" href="#FDOPT_NORETRY"><code class="Dv">FDOPT_NORETRY</code></a></dt> - <dd>Do not retry operations on failure</dd> - <dt id="FDOPT_SILENT"><a class="permalink" href="#FDOPT_SILENT"><code class="Dv">FDOPT_SILENT</code></a></dt> - <dd>Do not print error messages to the console</dd> - </dl> - </dd> - <dt id="FDIOCGETOPTS"><a class="permalink" href="#FDIOCGETOPTS"><code class="Dv">FDIOCGETOPTS</code></a> - <var class="Fa">int</var></dt> - <dd>Fetch drive options.</dd> -</dl> -<p class="Pp">A typical use of the formatting facilities would be to open the - device, call <code class="Dv">FDIOCGETFORMAT</code> to fetch the current - format parameters, perhaps change a parameter or two, display the formatting - details to the user, and then call <code class="Dv">FDIOCSETFORMAT</code> - followed by a series of calls to - <code class="Dv">FDIOCFORMAT_TRACK</code>.</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">fdformat(1)</a>, <a class="Xr">acpi(4)</a>, - <a class="Xr">isa(4)</a>, <a class="Xr">pnpbios(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">fdc</code> formatting support appeared in - <span class="Ux">NetBSD 1.3</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">September 23, 2011</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/fwhrng.4 4.html b/static/netbsd/man4/man4.x86/fwhrng.4 4.html deleted file mode 100644 index 4bd09938..00000000 --- a/static/netbsd/man4/man4.x86/fwhrng.4 4.html +++ /dev/null @@ -1,44 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">FWHRNG(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">FWHRNG(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">fwhrng</code> — <span class="Nd">Intel - Firmware Hub Random Number Generator</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">fwhrng* at ichlpcib?</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">fwhrng</code> driver provides support for - hardware Random Number Generator (RNG) available on some Intel Firmware Hubs - (FWHs). The <code class="Nm">fwhrng</code> driver accesses the RNG through - an I/O controller hub (ICH).</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">rnd(4)</a>, <a class="Xr">x86/ichlpcib(4)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Intel 82802AB/82802AC Firmware Hub (FWH)</span>, - <a class="RsU" href="http://download.intel.com/design/chipsets/datashts/29065804.pdf">http://download.intel.com/design/chipsets/datashts/29065804.pdf</a>, - <span class="RsD">November, 2000</span>.</cite></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1> -<p class="Pp">The entropy source is not tested for randomness.</p> -</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.x86/hpet.4 4.html b/static/netbsd/man4/man4.x86/hpet.4 4.html deleted file mode 100644 index 4dc1454d..00000000 --- a/static/netbsd/man4/man4.x86/hpet.4 4.html +++ /dev/null @@ -1,54 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">HPET(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">HPET(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">hpet</code> — <span class="Nd">High - Precision Event Timer</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">hpet* at acpihpetbus?</code> - <br/> - <code class="Cd">hpet* at acpinodebus?</code> - <br/> - <code class="Cd">hpet* at amdpcib?</code> - <br/> - <code class="Cd">hpet* at ichlpcib?</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">hpet</code> driver supports High Precision - Event Timers (HPETs). The HPET architecture defines one main 64-bit counter - and several additional timers with variable width. The minimum clock - frequency of the main timecounter is 10 MHz, but much higher rates are - common. The additional 32 or 64 -bit parts are typically accessible via MMIO - that is set by the system BIOS through ACPI.</p> -<p class="Pp">As a HPET can provide higher interrupt rates than a RTC or - <a class="Xr">attimer(4)</a>, multimedia is one typical application context. - The interrupt logic is configurable through I/O APIC, but a legacy mode is - provided for 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>, <a class="Xr">attimer(4)</a>, - <a class="Xr">timecounter(9)</a>, <a class="Xr">tsc(9)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">IA-PC HPET (High Precision Event Timers) - Specification</span>, <span class="RsN">Revision 1.0a</span>, - <a class="RsU" href="http://www.intel.com/hardwaredesign/hpetspec_1.pdf">http://www.intel.com/hardwaredesign/hpetspec_1.pdf</a>, - <span class="RsD">October, 2004</span>.</cite></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">June 14, 2011</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/ichlpcib.4 3.html b/static/netbsd/man4/man4.x86/ichlpcib.4 3.html deleted file mode 100644 index 985e08bf..00000000 --- a/static/netbsd/man4/man4.x86/ichlpcib.4 3.html +++ /dev/null @@ -1,95 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">ICHLPCIB(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">ICHLPCIB(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">ichlpcib</code> — <span class="Nd">Intel - ICH LPC Interface Bridge</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">ichlpcib* at pci? dev ? function ?</code> - <br/> - <code class="Cd">fwhrng* at ichlpcib?</code> - <br/> - <code class="Cd">hpet0 at ichlpcib?</code> - <br/> - <code class="Cd">isa0 at ichlpcib?</code> - <br/> - <code class="Cd">gpio* at ichlpcib?</code> - <br/> - <code class="Cd">tco* at ichlpcib?</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">ichlpcib</code> driver supports the Intel ICH - LPC Interface Bridges on compatible chipsets. Supported functions - include:</p> -<ul class="Bl-bullet"> - <li>Watchdog timer. The watchdog timer may be configured for a 1 seconds (on - ICH6 or newer) and 2 seconds (on ICH5 or older) min period and for a 23 - seconds (on ICH5 or older) or 367 seconds max period (on ICH6 or newer). - <p class="Pp">Prior to <span class="Ux">NetBSD 8.0</span>, the - <a class="Xr">x86/tco(4)</a> watchdog timer was included as part of the - <code class="Nm">ichlpcib</code> driver, and did not require explicit - configuration.</p> - </li> - <li>Power Management timer. A 24-bit timer available to be used by the - timecounters framework.</li> - <li>SpeedStep. In some older systems the SpeedStep function is also available, - and can be used to switch between high and low frequency (to reduce power - consumption) via the <code class="Li">machdep.speedstep_state</code> - <a class="Xr">sysctl(8)</a> node. A value of 0 will use the low frequency - (low power) and a 1 will enable the high frequency (full power).</li> - <li>General Purpose Input/Output. The ICH provides up to 64 I/O pins which can - be accessed through the <a class="Xr">gpio(4)</a> framework.</li> -</ul> -</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">gpio(4)</a>, <a class="Xr">x86/est(4)</a>, - <a class="Xr">x86/fwhrng(4)</a>, <a class="Xr">x86/hpet(4)</a>, - <a class="Xr">x86/ioapic(4)</a>, <a class="Xr">x86/tco(4)</a>, - <a class="Xr">sysctl(8)</a>, <a class="Xr">wdogctl(8)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Intel I/O Controller Hub 6 (ICH6) Family</span>, - <a class="RsU" href="http://www.intel.com/assets/pdf/datasheet/301473.pdf">http://www.intel.com/assets/pdf/datasheet/301473.pdf</a>, - <span class="RsD">January, 2005</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Intel I/O Controller Hub 7 (ICH7) Family</span>, - <a class="RsU" href="http://www.intel.com/Assets/PDF/datasheet/307013.pdf">http://www.intel.com/Assets/PDF/datasheet/307013.pdf</a>, - <span class="RsD">April, 2007</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Intel I/O Controller Hub 8 (ICH8) Family</span>, - <a class="RsU" href="http://www.intel.com/assets/pdf/datasheet/313056.pdf">http://www.intel.com/assets/pdf/datasheet/313056.pdf</a>, - <span class="RsD">May, 2007</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Using the Intel ICH Family Watchdog Timer (WDT)</span>, - <a class="RsU" href="ftp://download.intel.com/design/chipsets/applnots/29227301.pdf">ftp://download.intel.com/design/chipsets/applnots/29227301.pdf</a>, - <span class="RsD">September, 2002</span>.</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">ichlpcib</code> driver first appeared in - <span class="Ux">NetBSD 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">ichlpcib</code> driver was written by - <span class="An">Minoura Makoto</span> and - <br/> - <span class="An">Matthew R. Green</span>.</p> -</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.x86/imcsmb.4 3.html b/static/netbsd/man4/man4.x86/imcsmb.4 3.html deleted file mode 100644 index 7b5477b3..00000000 --- a/static/netbsd/man4/man4.x86/imcsmb.4 3.html +++ /dev/null @@ -1,113 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">IMCSMB(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">IMCSMB(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">imcsmb</code> — <span class="Nd">Intel - integrated Memory Controller (iMC) SMBus controller 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">imc* at pci? dev ? func ?</code> - <br/> - <code class="Cd">imcsmb* at imc?</code> - <br/> - <code class="Cd">iic* at i2cbus?</code></p> -<p class="Pp">Alternatively, to load the driver as a module at boot time, place - the following line in <a class="Xr">boot.cfg(5)</a>:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">load=imcsmb</code></div> -<p class="Pp">or add the following line to your /etc/modules file:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">imcsmb</code></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">imcsmb</code> driver provides - <a class="Xr">iic(4)</a> support for the SMBus controller functionality in - the integrated Memory Controllers (iMCs) embedded in Intel Sandybridge-Xeon, - Ivybridge-Xeon, Haswell-Xeon, and Broadwell-Xeon CPUs. Each CPU implements - one or more iMCs, depending on the number of cores; each iMC implements two - SMBus controllers (iMC-SMBs). The iMC-SMBs are used by the iMCs to read - configuration information from the DIMMs during POST. They may also be used, - by motherboard firmware or a BMC, to monitor the temperature of the - DIMMs.</p> -<p class="Pp" id="not">The iMC-SMBs are - <a class="permalink" href="#not"><b class="Sy">not</b></a> general-purpose - SMBus controllers. By their nature, they are only ever attached to DIMMs, so - they implement only the SMBus operations needed for communicating with - DIMMs. Specifically:</p> -<p class="Pp"></p> -<ul class="Bl-dash Bd-indent Bl-compact"> - <li>READB</li> - <li>READW</li> - <li>WRITEB</li> - <li>WRITEW</li> -</ul> -<p class="Pp">A more detailed discussion of the hardware and driver architecture - can be found at the top of <span class="Pa">sys/dev/imcsmb/imc.c</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="WARNINGS"><a class="permalink" href="#WARNINGS">WARNINGS</a></h1> -<p class="Pp">As mentioned above, firmware might use the iMC-SMBs to read DIMM - temperatures. The public iMC documentation does not describe any sort of - coordination mechanism to prevent requests from different sources — - such as the motherboard firmware, a BMC, or the operating system — - from interfering with each other.</p> -<p class="Pp"></p> -<div class="Bf Sy">Therefore, it is highly recommended that developers contact - the motherboard vendor for any board-specific instructions on how to disable - and re-enable DIMM temperature monitoring.</div> -<p class="Pp" id="imcsmb_pci_request_bus">DIMM temperature monitoring should be - disabled before returning from - <a class="permalink" href="#imcsmb_pci_request_bus"><code class="Fn">imcsmb_pci_request_bus</code></a>(), - and re-enabled before returning from - <a class="permalink" href="#imcsmb_pci_release_bus"><code class="Fn" id="imcsmb_pci_release_bus">imcsmb_pci_release_bus</code></a>(). - The driver includes comments to that effect at the appropriate locations. - The driver has been tested and shown to work, with only that type of - modification, on certain motherboards from Intel. (Unfortunately, those - modifications were based on material covered under a non-disclosure - agreement, and therefore are not included in this driver.) The driver has - also been tested and shown to work as-is on various motherboards from - SuperMicro and ASUS.</p> -<p class="Pp">Because of the above, the <code class="Nm">imcsmb</code> driver is - not included in the default <code class="Dv">GENERIC</code> kernel. In order - to use the <code class="Nm">imcsmb</code> driver, you must compile a custom - kernel, or load the driver using <a class="Xr">modload(8)</a>.</p> -<p class="Pp">The <a class="Xr">iic(4)</a> driver will connect to the i2cbus - instances created by <code class="Nm">imcsmb</code>.</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">iic(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">imcsmb</code> driver first appeared in - <span class="Ux">FreeBSD 12.0</span>. It was later ported to - <span class="Ux">NetBSD 9.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">imcsmb</code> driver was originally written - for Panasas by <span class="An">Joe Kloss</span>. It was substantially - refactored, and this manual page was written, by <span class="An">Ravi - Pokala</span> - <<a class="Mt" href="mailto:rpokala@freebsd.org">rpokala@freebsd.org</a>>. - It was adapted to <span class="Ux">NetBSD</span> by <span class="An">Paul - Goyette</span> - <<a class="Mt" href="mailto:pgoyette@NetBSD.org">pgoyette@NetBSD.org</a>>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 16, 2020</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/lpt.4 4.html b/static/netbsd/man4/man4.x86/lpt.4 4.html deleted file mode 100644 index 20149a8f..00000000 --- a/static/netbsd/man4/man4.x86/lpt.4 4.html +++ /dev/null @@ -1,75 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">LPT(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">LPT(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">lpt</code> — <span class="Nd">Parallel - port 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">lpt0 at isa? port "IO_LPT1" irq - 7</code> - <br/> - <code class="Cd">lpt1 at isa? port "IO_LPT2"</code> - <br/> - <code class="Cd">lpt* at acpi?</code> - <br/> - <code class="Cd">lpt* at ofisa?</code> - <br/> - <code class="Cd">lpt* at pnpbios? index ?</code> - <br/> - <code class="Cd">lpt* at puc? port ?</code></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">This driver provides access to parallel ports. The bits in the - minor number select various features of the driver. If no IRQ is specified - in the kernel configuration, only the polling device may be used.</p> -<table class="Bl-column Bd-indent"> - <tr id="Minor"> - <td><a class="permalink" href="#Minor"><b class="Sy">Minor Bit</b></a></td> - <td>Function</td> - </tr> - <tr> - <td>128</td> - <td>Use the interruptless driver. (polling)</td> - </tr> - <tr> - <td>64</td> - <td>Do not initialize the device on the port.</td> - </tr> - <tr> - <td>32</td> - <td>Automatic LF on CR.</td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1> -<dl class="Bl-tag Bl-compact"> - <dt><span class="Pa">/dev/lpt0</span></dt> - <dd>first interrupt-driven parallel port device</dd> - <dt><span class="Pa">/dev/lpa0</span></dt> - <dd>first polled parallel port device</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">acpi(4)</a>, <a class="Xr">isa(4)</a>, - <a class="Xr">ofisa(4)</a>, <a class="Xr">pnpbios(4)</a>, - <a class="Xr">puc(4)</a></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">September 23, 2011</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/mem.4 4.html b/static/netbsd/man4/man4.x86/mem.4 4.html deleted file mode 100644 index d712ca60..00000000 --- a/static/netbsd/man4/man4.x86/mem.4 4.html +++ /dev/null @@ -1,49 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">MEM(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">MEM(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">mem</code>, <code class="Nm">kmem</code> — - <span class="Nd">memory files</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The special file <code class="Nm">/dev/mem</code> is an interface - to the physical memory of the computer. Byte offsets in this file are - interpreted as physical memory addresses. Reading and writing this file is - equivalent to reading and writing memory itself. Only offsets within the - bounds of <code class="Nm">/dev/mem</code> are allowed.</p> -<p class="Pp">Kernel virtual memory is accessed through the interface - <code class="Nm">/dev/kmem</code> in the same manner as - <code class="Nm">/dev/mem</code>. Only kernel virtual addresses that are - currently mapped to memory are allowed.</p> -<p class="Pp">On ISA the I/O memory space begins at physical address 0x000a0000 - and runs to 0x00100000.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1> -<dl class="Bl-tag Bl-compact"> - <dt><span class="Pa">/dev/mem</span></dt> - <dd style="width: auto;"> </dd> - <dt><span class="Pa">/dev/kmem</span></dt> - <dd style="width: auto;"> </dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">mem</code>, <code class="Nm">kmem</code> - files appeared in <span class="Ux">Version 6 AT&T - UNIX</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">March 27, 2026</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/odcm.4 4.html b/static/netbsd/man4/man4.x86/odcm.4 4.html deleted file mode 100644 index 9a5745fa..00000000 --- a/static/netbsd/man4/man4.x86/odcm.4 4.html +++ /dev/null @@ -1,59 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">ODCM(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">ODCM(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">odcm</code> — <span class="Nd">On-demand - Clock Modulation</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">odcm0 at cpu0</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">odcm</code> driver provides support for - changing the duty cycle of a CPU. This is sometimes known as - “on-demand clock modulation” (ODCM). Refer to - <a class="Xr">acpicpu(4)</a> for additional details about ODCM.</p> -<p class="Pp">The following <a class="Xr">sysctl(8)</a> variables are available - with <code class="Nm">odcm</code>:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="machdep.clockmod.target"><a class="permalink" href="#machdep.clockmod.target"><code class="Ic">machdep.clockmod.target</code></a></dt> - <dd>The target duty cycle of all CPUs. The values range from 7 (100 %) to 0 - (approximately 13 %).</dd> - <dt id="machdep.clockmod.current"><a class="permalink" href="#machdep.clockmod.current"><code class="Ic">machdep.clockmod.current</code></a></dt> - <dd>The current duty cycle of CPUs.</dd> - <dt id="machdep.clockmod.available"><a class="permalink" href="#machdep.clockmod.available"><code class="Ic">machdep.clockmod.available</code></a></dt> - <dd>A list of available duty cycles.</dd> -</dl> -</div> -<p class="Pp">Note that some errata may limit the availability of some duty - cycles.</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">acpicpu(4)</a>, <a class="Xr">x86/est(4)</a>, - <a class="Xr">x86/powernow(4)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1> -<p class="Pp">ODCM is meant for short-term thermal management, not power - management. There is usually no reason for a system administrator to change - the values manually. Lowering the duty cycle may dramatically decrease - performance and responsiveness of the system.</p> -</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.x86/powernow.4 4.html b/static/netbsd/man4/man4.x86/powernow.4 4.html deleted file mode 100644 index 8e2ea4c8..00000000 --- a/static/netbsd/man4/man4.x86/powernow.4 4.html +++ /dev/null @@ -1,57 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">POWERNOW(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">POWERNOW(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">powernow</code> — <span class="Nd">AMD - PowerNow! and Cool'n'Quiet</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">powernow0 at cpu0</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">powernow</code> driver supports AMD - “PowerNow!” and “Cool'n'Quiet” CPU frequency - scaling technologies. The following <a class="Xr">sysctl(8)</a> variables - are available with <code class="Nm">powernow</code>:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="machdep.cpu.frequency.target"><a class="permalink" href="#machdep.cpu.frequency.target"><code class="Ic">machdep.cpu.frequency.target</code></a></dt> - <dd>The target frequency of the CPUs.</dd> - <dt id="machdep.cpu.frequency.current"><a class="permalink" href="#machdep.cpu.frequency.current"><code class="Ic">machdep.cpu.frequency.current</code></a></dt> - <dd>The current frequency.</dd> - <dt id="machdep.cpu.frequency.available"><a class="permalink" href="#machdep.cpu.frequency.available"><code class="Ic">machdep.cpu.frequency.available</code></a></dt> - <dd>The available frequencies.</dd> -</dl> -</div> -<p class="Pp">Note, however, that these variables are not guaranteed to exist in - the future versions of <span class="Ux">NetBSD</span>.</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">acpicpu(4)</a>, <a class="Xr">x86/est(4)</a>, - <a class="Xr">x86/odcm(4)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1> -<p class="Pp">The <code class="Nm">powernow</code> driver is considered a legacy - interface to be used only with relatively old systems. The driver supports - only AMD processor families K7 (for instance, Duron, Athlon, and some - Semprons) and K8 (namely, the early 64-bit family, including Athlon 64, - Opteron, and Turion).</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">September 7, 2020</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/soekrisgpio.4 4.html b/static/netbsd/man4/man4.x86/soekrisgpio.4 4.html deleted file mode 100644 index 78bec8ac..00000000 --- a/static/netbsd/man4/man4.x86/soekrisgpio.4 4.html +++ /dev/null @@ -1,64 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">SOEKRIS(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">SOEKRIS(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">soekrisgpio</code> — - <span class="Nd">Soekris net6501 GPIO and LEDs</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">soekrisgpio0 at isa? port 0x680</code> - <br/> - <code class="Cd">gpio* at soekrisgpio?</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">soekrisgpio</code> driver provides support - for the GPIO and LEDs as implemented by the Xilinx Spartan FGPA integrated - into the Soekris net6501 programmed with the default bitstream found in the - BIOS.</p> -<p class="Pp">Two standard <a class="Xr">gpio(4)</a> interfaces are provided, - one for the 16 real pins which can be configured as either inputs or outputs - and another with 2 output-only pins that map to the error and ready LEDs - respectively. Both may be used with <a class="Xr">gpioctl(8)</a>.</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">gpio(4)</a>, <a class="Xr">intro(4)</a>, - <a class="Xr">isa(4)</a>, <a class="Xr">gpioctl(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">soekrisgpio</code> driver first appeared in - <span class="Ux">NetBSD 7.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">soekrisgpio</code> driver was written by - <span class="An">Matt Dainty</span> - <<a class="Mt" href="mailto:matt@...">matt@...</a>> and imported from - a patch for <span class="Ux">OpenBSD</span> to - <span class="Ux">NetBSD</span> by - <br/> - <span class="An">Frank Kardel</span> - <<a class="Mt" href="mailto:kardel@NetBSD.org">kardel@NetBSD.org</a>>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">If the Xilinx FPGA is programmed with a different bitstream, the - driver will likely not function.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">June 10, 2013</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/tco.4 4.html b/static/netbsd/man4/man4.x86/tco.4 4.html deleted file mode 100644 index d5fa68f4..00000000 --- a/static/netbsd/man4/man4.x86/tco.4 4.html +++ /dev/null @@ -1,57 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">TCO(4)</td> - <td class="head-vol">Device Drivers Manual (x86)</td> - <td class="head-rtitle">TCO(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">tco</code> — <span class="Nd">Intel - Controller Hub TCO watchdog timer device</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">tco* at ichlpcib?</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">tco</code> driver provides support for the - watchdog timer included in the Intel Controller Hub (ICH).</p> -<p class="Pp">Setting the timer interval and arming the watchdog is performed - using the <a class="Xr">wdogctl(8)</a> utility. For ICH5 and earlier - controllers, the interval is in the range of 2 to 23 seconds; for ICH6 and - newer controllers, the interval is in the range of 1 to 367 seconds.</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">wdogctl(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">tco</code> driver first appeared in - <span class="Ux">NetBSD 8.0</span>. In earlier releases of - <span class="Ux">NetBSD</span> the driver was included as part of the - <a class="Xr">x86/ichlpcib(4)</a> driver.</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">tco</code> driver was written by - <span class="An">Minoura Makoto</span> - <<a class="Mt" href="mailto:minoura@NetBSD.org">minoura@NetBSD.org</a>> - and <span class="An">Matthew R. Green</span> - <<a class="Mt" href="mailto:mrg@NetBSD.org">mrg@NetBSD.org</a>>. The - <code class="Nm">tco</code> driver was separated from the - <a class="Xr">x86/ichlpcib(4)</a> driver by <span class="An">Paul - Goyette</span> - <<a class="Mt" href="mailto:pgoyette@NetBSD.org">pgoyette@NetBSD.org</a>>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 4, 2015</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man4/man4.x86/viac7temp.4 4.html b/static/netbsd/man4/man4.x86/viac7temp.4 4.html deleted file mode 100644 index c94245a3..00000000 --- a/static/netbsd/man4/man4.x86/viac7temp.4 4.html +++ /dev/null @@ -1,41 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">VIAC7TEMP(4)</td> - <td class="head-vol">Device Drivers Manual</td> - <td class="head-rtitle">VIAC7TEMP(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">viac7temp</code> — <span class="Nd">VIA - C7, VIA Nano and Zhaoxin CPU temperature sensor</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">viac7temp* at cpu?</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">viac7temp</code> driver supports temperature - sensors found in VIA C7, VIA Nano and Zhaoxin processors. The available - information is available through the <a class="Xr">envsys(4)</a> API and the - <a class="Xr">envstat(8)</a> command.</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">coretemp(4)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp"><span class="An">Jared D. McNeill</span> - <<a class="Mt" href="mailto:jmcneill@invisible.ca">jmcneill@invisible.ca</a>></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 30, 2024</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |