Prep work for merging Power and Resource Management and Using and

Debugging FreeBSD ACPI

Sponsored by:	iXsystems

1 files changed, 51 insertions, 61 deletions

diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.xml b/en_US.ISO8859-1/books/handbook/config/chapter.xml
index 2846617df5..9d9cdf8d5f 100644
--- a/en_US.ISO8859-1/books/handbook/config/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/config/chapter.xml
@@ -2838,57 +2838,25 @@ kern.maxvnodes: 100000</screen>
     </info>
 
     <para>It is important to utilize hardware resources in an
-      efficient manner.  Before the Advanced Configuration and Power
-      Interface (<acronym>ACPI</acronym>) was introduced, it was
-      difficult and inflexible for operating systems to manage the
-      power usage and thermal properties of a system.  The hardware
-      was managed by the <acronym>BIOS</acronym> and the user had less
-      control and visibility into the power management settings.  Some
-      limited configurability was available via <emphasis>Advanced
-	Power Management (<acronym>APM</acronym>)</emphasis>.  Power
-      and resource management allows the operating system to monitor
-      system limits and to possibly provide an alert if the system
-      temperature increases unexpectedly.</para>
-
-    <para>This section provides comprehensive information about
-      <acronym>ACPI</acronym>.  References will be provided for
-      further reading.</para>
-
-    <sect2 xml:id="acpi-intro">
-      <title>What Is ACPI?</title>
-
-      <indexterm>
-	<primary>ACPI</primary>
-      </indexterm>
-
-      <indexterm>
-	<primary>APM</primary>
-      </indexterm>
-
-      <para><acronym>ACPI</acronym> is a standard written by an
-	alliance of vendors to provide a standard interface for
-	hardware resources and power management.  It is a key
-	element in <emphasis>Operating System-directed configuration
-	and Power Management</emphasis> as it provides more control
-	and flexibility to the operating system.  Modern systems
-	<quote>stretched</quote> the limits of the current Plug and
-	Play interfaces prior to the introduction of
-	<acronym>ACPI</acronym>.  <acronym>ACPI</acronym> is the
-	direct successor to <acronym>APM</acronym>.</para>
-    </sect2>
-
-    <sect2 xml:id="acpi-old-spec">
-      <title>Shortcomings of Advanced Power Management</title>
-
-      <para>The <acronym>APM</acronym> facility controls the power
-	usage of a system based on its activity.  The
-	<acronym>APM</acronym> <acronym>BIOS</acronym> is supplied
-	by the vendor and is specific to the hardware platform.  An
-	<acronym>APM</acronym> driver in the operating system
-	mediates access to the <emphasis><acronym>APM</acronym>
-	  Software Interface</emphasis>, which allows management of
-	power levels.  <acronym>APM</acronym> should still be used
-	for systems manufactured at or before the year 2000.</para>
+      efficient manner.  Power and resource management allows the
+      operating system to monitor system limits and to possibly
+      provide an alert if the system temperature increases
+      unexpectedly.  An early specification for providing power
+      management was the Advanced Power Management
+      (<acronym>APM</acronym>) facility.  <acronym>APM</acronym>
+      controls the power usage of a system based on its activity.
+      However, it was difficult and inflexible for operating systems
+      to manage the power usage and thermal properties of a system.
+      The hardware was managed by the <acronym>BIOS</acronym> and the
+      user had limited configurability and visibility into the power
+      management settings.  The <acronym>APM</acronym>
+      <acronym>BIOS</acronym> is supplied by the vendor and is
+      specific to the hardware platform.  An <acronym>APM</acronym>
+      driver in the operating system mediates access to the
+      <acronym>APM</acronym> Software Interface, which allows
+      management of power levels.  <acronym>APM</acronym> should still
+      be used for systems manufactured at or before the year
+      2000.</para>
 
       <para>There are four major problems in <acronym>APM</acronym>.
 	First, power management is done by the vendor-specific
@@ -2918,11 +2886,37 @@ kern.maxvnodes: 100000</screen>
 	many situations.  <acronym>PNPBIOS</acronym> is 16-bit
 	technology, so the operating system has to use 16-bit
 	emulation in order to interface with
-	<acronym>PNPBIOS</acronym> methods.</para>
-
-      <para>The &os; <acronym>APM</acronym> driver is documented in
+	<acronym>PNPBIOS</acronym> methods.  &os; provides an
+	<acronym>APM</acronym> driver for backwards compatibility with
+	older hardware.  The driver is documented in
 	&man.apm.4;.</para>
-    </sect2>
+
+      <indexterm>
+	<primary>ACPI</primary>
+      </indexterm>
+
+      <indexterm>
+	<primary>APM</primary>
+      </indexterm>
+
+    <para>The successor to <acronym>APM</acronym> is the Advanced
+      Configuration and Power Interface (<acronym>ACPI</acronym>).
+      <acronym>ACPI</acronym> is a standard written by an
+	alliance of vendors to provide a standard interface for
+	hardware resources and power management.  It is a key
+	element in <emphasis>Operating System-directed configuration
+	and Power Management</emphasis> as it provides more control
+	and flexibility to the operating system.  Modern systems
+	stretched the limits of the current Plug and
+	Play interfaces prior to the introduction of
+	<acronym>ACPI</acronym>..</para>
+
+      <para>This chapter demonstrates how to configure
+	<acronym>ACPI</acronym> on &os;.  It then offers some tips on
+	how to debug <acronym>ACPI</acronym> and how to submit a
+	problem report containing debugging information so that
+	developers can diagnosis and fix <acronym>ACPI</acronym>
+	issues.</para>
 
     <sect2 xml:id="acpi-config">
       <title>Configuring <acronym>ACPI</acronym></title>
@@ -2963,11 +2957,10 @@ kern.maxvnodes: 100000</screen>
       <para>Other options are available via &man.sysctl.8;.  Refer to
 	&man.acpi.4; and &man.acpiconf.8; for more information.</para>
     </sect2>
-  </sect1>
 
-  <sect1 xml:id="ACPI-debug">
+  <sect2 xml:id="ACPI-submitdebug">
     <info>
-      <title>Using and Debugging &os; <acronym>ACPI</acronym></title>
+      <title>Debugging &os; <acronym>ACPI</acronym></title>
 
       <authorgroup>
 	<author>
@@ -3018,9 +3011,6 @@ kern.maxvnodes: 100000</screen>
       cause of problems and in debugging and developing a
       solution.</para>
 
-    <sect2 xml:id="ACPI-submitdebug">
-      <title>Submitting Debugging Information</title>
-
       <note>
 	<para>Before submitting a problem, ensure the latest
 	  <acronym>BIOS</acronym> version is installed and, if