From: "Cintia B. Margi" <cintia-Emgmuai4XwL2fBVCVOL8/A@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: question about ACPI & Smart Batteries
Date: Thu, 12 Aug 2004 15:29:36 -0700 [thread overview]
Message-ID: <20040812222936.GD30862@miramar.cse.ucsc.edu> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A8470726AFF5-sBd4vmA9Se6krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
* Grover, Andrew (andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org) said:
> Unless you have a Fujitsu Uva, you do not have a smart battery, you have
> a control method battery.
I don't have a smart battery then.
> For a CM battery, the OS can poll the battery state by calling _BST, or
> set a trip point (via _BTP) and the OS will get an interrupt when the
> battery crosses that trip.
I do not want to set a trip point, but I would like to monitor the battery discharge
process... I want to characterize the battery discharge behavior under different tasks,
so I intend to monitor the battery voltage and the discharge rate (which I can obtain
from /proc/acpi/battery/BAT0/state). What I would like to know is how often the state
file is updated and how accurate these values are. Any idea where I can get this info?
Thanks,
Cintia
--
Cintia Margi
Graduate Student
SoE - UCSC
http://www.soe.ucsc.edu/~cintia
GPG Public Key: http://www.soe.ucsc.edu/~cintia/cintia.gpg
B4DE 9355 3840 FF72 50F2 ACAC E2EC AA9A 41E2 CD55
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2004-08-12 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 22:10 question about ACPI & Smart Batteries Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A8470726AFF5-sBd4vmA9Se6krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-12 22:29 ` Cintia B. Margi [this message]
[not found] ` <20040812222936.GD30862-v28VZnYc+MmC5P5rv/TENfZ8FUJU4vz8@public.gmane.org>
2004-08-12 22:36 ` Tomasz Ciolek
2004-08-12 22:40 ` Paul Ionescu
[not found] ` <pan.2004.08.12.22.40.32.120142-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
2004-08-13 7:40 ` Karol Kozimor
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 22:02 Cintia B. Margi
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=20040812222936.GD30862@miramar.cse.ucsc.edu \
--to=cintia-emgmuai4xwl2fbvcvol8/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.