As requested by deraadt, split acpi(4) up into individual driver pages.

While doing this, improve and add the text of some manuals.  Some of
these are simply revived versions of the pages back from when they were
individual pages.

Input and ok from jmc.

Note:  When we wrote these pages, people submitted new pages to jmc and
I.  At some point during this, we decided to merge all pages into acpi(4)
(which is now being undone), and I lost track of who sent what.  Thus,
if you think you should be the copyright owner of any of these files,
get back to me in private.

1 files changed, 7 insertions, 128 deletions

diff --git a/share/man/man4/acpi.4 b/share/man/man4/acpi.4
index 1047114bed2..e761bec8258 100644
--- a/share/man/man4/acpi.4
+++ b/share/man/man4/acpi.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: acpi.4,v 1.16 2006/12/25 01:06:45 mk Exp $
+.\"	$OpenBSD: acpi.4,v 1.17 2007/01/10 16:14:36 mk Exp $
 .\"
 .\" Copyright (c) 2006 Alexander Yurchenko <grange@openbsd.org>
 .\"
@@ -18,24 +18,10 @@
 .Dt ACPI 4
 .Os
 .Sh NAME
-.Nm acpi ,
-.Nm acpiac ,
-.Nm acpibat ,
-.Nm acpibtn ,
-.Nm acpiec ,
-.Nm acpihpet ,
-.Nm acpitimer ,
-.Nm acpitz
+.Nm acpi
 .Nd Advanced Configuration and Power Interface
 .Sh SYNOPSIS
 .Cd "acpi0 at mainbus?"
-.Cd "acpiac* at acpi?"
-.Cd "acpibat* at acpi?"
-.Cd "acpibtn* at acpi?"
-.Cd "acpiec* at acpi?"
-.Cd "acpihpet* at acpi?"
-.Cd "acpitimer* at acpi?"
-.Cd "acpitz* at acpi?"
 .Pp
 .Cd "option ACPIVERBOSE"
 .Cd "option ACPI_ENABLE"
@@ -46,71 +32,6 @@ driver provides basic support for ACPI including loading ACPI tables from
 the firmware, parsing and interpreting AML code, event handling,
 suspending and powering off, and attaching device drivers.
 .Pp
-The
-.Nm acpiac
-driver supports ACPI AC Adapters.
-Information about AC power source status (connected or disconnected) is
-available through this driver.
-AC power source status is updated every 10 seconds or,
-if the implementation supports it,
-via an event.
-.Pp
-The
-.Nm acpibat
-driver supports the ACPI Control Method Battery interface between the
-battery and the host.
-Information about the battery, such as capacity, recharge rate, voltage,
-and serial number, is available through this driver.
-Battery status is updated every 10 seconds or,
-if the implementation supports it,
-via an event.
-.Pp
-The
-.Nm acpibtn
-driver is used to power down the system safely when the user presses
-an ACPI power button
-.Pq usually the main system power button .
-.Pp
-The
-.Nm acpiec
-driver supports ACPI Embedded Controllers.
-It provides embedded controller access for other ACPI devices.
-On many systems
-which have an
-.Nm acpiec
-device, other ACPI devices such as
-.Nm acpiac ,
-.Nm acpibat ,
-and
-.Nm acpitz
-implicitly depend on the
-.Nm acpiec
-device.
-.Pp
-The
-.Nm acpihpet
-driver provides support for the high precision event timer to be used
-as a timecounter for the
-.Xr tc_init 9
-framework.
-.Pp
-The
-.Nm acpitimer
-driver allows access to a power management timer through the ACPI.
-The timer is used as a timecounter for the
-.Xr tc_init 9
-framework.
-.Pp
-The
-.Nm acpitz
-driver supports ACPI Thermal Zones.
-Temperature information is available through this driver as a sensor
-which is updated every 10 seconds or, if the implementation supports it,
-via an event.
-If the temperature exceeds the
-.Sq critical
-temperature threshold, the system will be shut down and powered off.
-.Pp
 If the configuration option
 .Dq Dv ACPIVERBOSE
 is set, information about all detected ACPI devices will be displayed
@@ -124,60 +45,18 @@ driver will take control of ACPI from the firmware (BIOS).
 WARNING: this may cause an overheating on some machines since
 .Nm
 doesn't provide any thermal or cooling control.
-.Pp
-Some devices, such as
-.Nm acpiac ,
-provide hardware information via sensors
-that can be monitored using
-.Xr sysctl 8
-or
-.Xr sensorsd 8 .
 .Sh SEE ALSO
-.Xr intro 4 ,
-.Xr sensorsd 8 ,
-.Xr sysctl 8 ,
-.Xr tc_init 9
+.Xr intro 4
 .Sh HISTORY
 The
-.Nm acpi ,
-.Nm acpiac ,
-.Nm acpibat ,
-.Nm acpiec ,
-.Nm acpihpet ,
-.Nm acpitimer ,
-and
-.Nm acpitz
-drivers first appeared in
+.Nm
+driver first appeared in
 .Ox 3.8 .
 .Sh AUTHORS
 .An -nosplit
 The
-.Nm acpi ,
-.Nm acpihpet ,
-and
-.Nm acpitimer
-drivers were written by
+.Nm
+driver was written by
 .An Thorsten Lockert Aq tholo@sigmasoft.com
 and
 .An Jordan Hargrave Aq jordan@openbsd.org .
-.Pp
-The
-.Nm acpiac ,
-.Nm acpibat ,
-and
-.Nm acpibtn
-drivers were written by
-.An Marco Peereboom Aq marco@openbsd.org .
-.Pp
-The
-.Nm acpiec
-and
-.Nm acpitz
-drivers were written by
-.An Can Erkin Acar Aq canacar@openbsd.org .
-.Sh BUGS
-Some systems do not propagate battery insertion up to the driver or
-will not report valid information unless there is a state change to the
-battery.
-.Pp
-Smart Battery Specification-based batteries are not supported.