From: Karl Hegbloom <hegbloom-tbDHPZwbsQQ@public.gmane.org>
To: ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Warn user when battery goes critical
Date: Mon, 05 Apr 2004 18:21:03 -0700 [thread overview]
Message-ID: <1081214462.2348.35.camel@localhost.localdomain> (raw)
In-Reply-To: <20040405211032.GA3575-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
On Mon, 2004-04-05 at 14:10, Pavel Machek wrote:
> When battery is going critical, perhaps user should know? It already
> helped me when power was turned off at expansion cord...
>
> + int res = acpi_battery_get_status(battery, &bst);
If this patch goes in, PLEASE, create a way to turn that feature OFF or
to control the interval at which it is run, since on some laptops (this
one) the battery status BIOS call takes too long, interrupts are
disabled then, and touch-pad and keyboard interrupts are lost, causing
pointer warps, bouncy or "stickyyyyyyyyyyyy" keys, and keyboard
lockouts. It is also probably the cause of a system hang during heavy
network I/O.
--
If you feel like the machines are conspiring against you,
then it's time to perspire against the machines.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-04-06 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 21:10 Warn user when battery goes critical Pavel Machek
[not found] ` <20040405211032.GA3575-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-04-06 1:21 ` Karl Hegbloom [this message]
2004-04-08 17:15 ` Stefan Seyfried
[not found] ` <20040408171527.GH23710-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-04-12 20:45 ` Sérgio Monteiro Basto
[not found] ` <1081802715.3428.40.camel-4/PLUo9XfK8@public.gmane.org>
2004-04-13 20:02 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1081214462.2348.35.camel@localhost.localdomain \
--to=hegbloom-tbdhpzwbsqq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox