Date: Sat, 25 Nov 2006 16:09:17 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: nate@root.org Cc: freebsd-acpi@freebsd.org Subject: Re: How do I... Message-ID: <20061125.160917.1628359610.imp@bsdimp.com> In-Reply-To: <4568AA2F.4050602@root.org> References: <20061124.201214.1656128345.imp@bsdimp.com> <4568AA2F.4050602@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <4568AA2F.4050602@root.org>
Nate Lawson <nate@root.org> writes:
: M. Warner Losh wrote:
: > ... run a command when there's < 1% battery life left?
: >
: > Warner
:
: You add support here in acpi_cmbat.c:
: /* XXX If all batteries are critical, perhaps we should suspend. */
: if (sc->bst.state & ACPI_BATT_STAT_CRITICAL) {
: if ((sc->flags & ACPI_BATT_STAT_CRITICAL) == 0) {
: sc->flags |= ACPI_BATT_STAT_CRITICAL;
: device_printf(dev, "critically low charge!\n");
: }
: }
:
: Use the acpi_NotifyMumble function to send a value to devd. You
: probably want to make sure you're off AC power also since you may still
: have that crit state when plugged in. So read the value of AC status
: (see kern_power.c for how to do this) before sending the notify.
I was thinking of sending the critical message as well as for each %
of battery life that changed. I just wanted to make sure that it
wasn't being done already and i was captain clueless.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061125.160917.1628359610.imp>
