From: simon-Ji7FXtOmRLs@public.gmane.org (Simon Fowler)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Battery rate on Acer TM 292
Date: Sat, 18 Sep 2004 01:15:09 +1000 [thread overview]
Message-ID: <20040917151509.GA7756@himi.org> (raw)
In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD305751B66D5-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
On Mon, Sep 13, 2004 at 09:20:53AM +0800, Li, Shaohua wrote:
> Please don't trust 'present rate'. In many systems, 'present rate' are
> always 0. If you want to estimate the power of the battery, please use
> remaining capacity. I'd like the user daemon use 'remaining capacity' to
> calculate the rate.
>
If present rate is reported, it's probably best to use it - the only
other alternative, sampling the remaining capacity over time,
is very error prone.
On my Fujitsu LifeBook p2120 present rate reliably reflects the
remaining battery life, even to the point of closely tracking
changes in power usage.
If I sample the remaining capacity every few seconds, however, it
becomes obvious that it simply doesn't update the reported value
often enough to be of much use - the smallest change in capacity
reported is around 30mAH, which is too coarse grained to allow a
good estimate. Even with averaging over a number of samples the
present rate calculated this way jumps around too much.
Probably the best approach would be to let the user choose which
approach to use, which is what I've done with wmacpi
(http://himi.org/wmacpi).
Simon
--
PGP public key Id 0x144A991C, or http://himi.org/stuff/himi.asc
(crappy) Homepage: http://himi.org
doe #237 (see http://www.lemuria.org/DeCSS)
My DeCSS mirror: ftp://himi.org/pub/mirrors/css/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-17 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 1:20 Battery rate on Acer TM 292 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD305751B66D5-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-09-13 5:39 ` Stefan Seyfried
2004-09-15 10:56 ` Stefan Tomanek
2004-09-17 15:15 ` Simon Fowler [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-12 12:47 Stefan Tomanek
[not found] ` <loom.20040912T144218-763-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2004-09-20 8:59 ` Norbert Preining
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=20040917151509.GA7756@himi.org \
--to=simon-ji7fxtomrls@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