From: Richard Black <richard.black-VXdhtT5mjnY@public.gmane.org>
To: ACPI Development - Sourceforge
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Battery "design capacity" incorrect
Date: Tue, 04 Mar 2003 08:16:24 -0600 [thread overview]
Message-ID: <3E64B538.20607@hp.com> (raw)
In-Reply-To: 1046723628.27050.3.camel@p2710
I see this patch (design capacity patch) at
http://sourceforge.net/projects/battstat/; however,
I don't see the 2 battery patch someone had not too long ago.
Whoever has the 2 battery patch, could you post it to
http://sourceforge.net/projects/battstat/?
Thanks in advance,
Richard Black
Troy Schultz wrote:
>>Correct. My main question is where is ACPI "getting" the 5400 from?
>>Various Windows tools, and even the manufacturer's specs claim "3860" or
>>"3870" as the capacity (tools and manufacturer respectively). I've
>>changed various Linux tools that I've written to do the math based on
>>the "last full capacity", but a lot of "other people's tools" use
>>"design capacity" which is "better", in my opinion as it can let you
>>know if you're having a calibration problem.
>>
>>
>
>I wonder if the design capacity in your case is the capacity of the
>battery if it were fully charged and then fully depleated, a situation
>which would and should never occurr. The last full capacity is what
>should be used in any calculation of percent charged as this will be
>changed to reflect the battery wear as the battery goes through its
>usefull life.
>
>I have made changes to the battstat applet I use to use the last full
>capacity in the calcualtions.
>
>Best Regards
>
>
--
Sincerely,
Richard Black
http://www.cpqlinux.com
http://www.compaq.com/linux
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
next prev parent reply other threads:[~2003-03-04 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 17:16 Battery "design capacity" incorrect Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A1C3-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-03-03 19:01 ` Matthew Keller
[not found] ` <1046718101.3209.60.camel-a2ysWtvtB4BRjtM+DFHcO/Z8FUJU4vz8@public.gmane.org>
2003-03-03 20:33 ` Troy Schultz
2003-03-04 14:16 ` Richard Black [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 19:11 Grover, Andrew
2003-03-01 18:15 Matthew Keller
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=3E64B538.20607@hp.com \
--to=richard.black-vxdhtt5mjny@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