cvs commit: src/usr.sbin/acpi/acpiconf acpiconf.c

[M. Warner Losh]

In message: <200403081501.55307.jhb at FreeBSD.org>
            John Baldwin <jhb at FreeBSD.org> writes:
: On Friday 05 March 2004 07:48 pm, Daniel O'Connor wrote:
: > On Sat, 6 Mar 2004 05:05, M. Warner Losh wrote:
: > > I've just added the following, based on the other ioctl that you can
: > > get battery info from:
: > >
: > > State:                  Present
: > > Rate:                   50000 mWh
: > > Cap:                    50000 mWh
: > > Volt:                   10.0 V
: > >
: > > Note: My battery/ACPI has a bug where 'RATE' and 'CAP' are always the
: > > same number.  I have a second bug where the CAP is listed as being
: > > more than the last full capacity of the battery.  This makes it very
: > > hard to do estimates for remaining battery life, but I'm not sure what
: > > can be done about it.
: >
: > I think you have to massage the data a fair bit to throw obvious outliers
: > away. Also I believe most implementations produce totally bogus values
: > during charging so you ignore rate when the battery is charging.
: 
: During charging, implementations are supposed to tell you how fast it is 
: charging so you can compute how much time is needed to get to a full charge, 
: not how much battery life time is left.  However, many BIOS's are broken.  My 
: old laptop never returned a sane value for rate and my new one always returns 
: a rate of 0, both of which violate the spec.  *sigh*

My Rate/Cap are always the same, even in charging/discharging
situations.  So my run time is always 1hr.  Rate should be 50000 mW/h

Warner