All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manish Prasad <mprasad-EX0cT3Az47bauI2f2gSDlQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Battery status update resolution
Date: Sun, 10 Aug 2003 02:14:08 -0400 (EDT)	[thread overview]
Message-ID: <Pine.GSO.4.53.0308100150310.8919@compserv2> (raw)
In-Reply-To: <Pine.GSO.4.53.0308092239430.8919-0/pBV72GoN7BkAz3hwFLjg@public.gmane.org>

Hi

I apologize upfront, if this is not totally relevant to this list.
Some questions about the update resolution of the battery remaining
capacity status:

What is the capacity status update resolution of a state-of-the-art
'smart' battery ? I'm currently using a Dell Inspiron 2600 with a Sanyo
LION control method battery, which updates its capacity status only for a
change of 30 - 40 mAh in the capacity (as observed through _BST control
method). What exactly is this limitation due to, is it the AML implementation
of the _BST method by the OEM or is it the battery hardware itself (say
number of bits in the A/D converter of the smart battery) ?

Any insights would be greatly appreciated.

Thanks,
--Manish





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

      parent reply	other threads:[~2003-08-10  6:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10  2:51 Owner ID wraparound problem during _BST Manish Prasad
     [not found] ` <Pine.GSO.4.53.0308092239430.8919-0/pBV72GoN7BkAz3hwFLjg@public.gmane.org>
2003-08-10  6:14   ` Manish Prasad [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=Pine.GSO.4.53.0308100150310.8919@compserv2 \
    --to=mprasad-ex0ct3az47baui2f2gsdlq@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 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.