From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: S Monteiro Basto <sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org>
Cc: Stefan Seyfried
<seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@public.gmane.org>,
hegbloom-tbDHPZwbsQQ@public.gmane.org,
acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: Warn user when battery goes critical
Date: Tue, 13 Apr 2004 22:02:51 +0200 [thread overview]
Message-ID: <20040413200251.GI468@openzaurus.ucw.cz> (raw)
In-Reply-To: <1081802715.3428.40.camel-4/PLUo9XfK8@public.gmane.org>
Hi!
> > > When battery is going critical, perhaps user should know? It already
> > > helped me when power was turned off at expansion cord...
> >
> > > + if (!res && (bst->state & 0x04))
> > > + printk(KERN_CRIT "Battery status: critical\n");
> >
> > This should go into userspace IMO. There are some applications that will
> > handle this, so no need for code bloat in the kernel.
> >
> > Hey! I'd never thought i could one day accuse Pavel of "eyecandy bloat" ;-)
> >
:-). Yes battery monitors exist and yes, I should watch
/proc/acpi/battery.../state; otoh it is clearly an critical condition,
and I should not be forced to run cpu-eating battery monitor daemon
when kernel knows without polling.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
-------------------------------------------------------
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
prev parent reply other threads:[~2004-04-13 20:02 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
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 [this message]
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=20040413200251.GI468@openzaurus.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=hegbloom-tbDHPZwbsQQ@public.gmane.org \
--cc=seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@public.gmane.org \
--cc=sergiomb-hHo3WeeoaswVhHzd4jOs4w@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