acpi battery rework patch

[Wilko Bulte]

On Mon, Jul 25, 2005 at 10:31:10PM -0700, Nate Lawson wrote..
> Wilko Bulte wrote:
> >>>On Sun, 24 Jul 2005 17:15:12 -0700
> >>>Nate Lawson <nate at root.org> wrote:
> >>Please try this patch with 7-current and report its output both on and 
> >>off power.  It prints out more debugging info each time the battery is 
> >>read.
> >
> >
> >On an Compaq EVO N160, on AC power
> >batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0
> >batt pass2: min 0 total_min 0 total_cap 0
> >ichss0: transition to 1 failed
> 
> This is a separate issue, you should disable ichss:
> hint.ichss.0.disabled="1"
> 
> It appears your chipset does not actually support it.  I think bruno@ 
> has a patch for doing more detailed checking for systems that actually 
> support it.
> 
> >batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0
> >batt pass2: min 0 total_min 0 total_cap 0
> >ichss0: transition to 1 failed
> >
> >APM version: 1.2
> >APM Management: Enabled
> >AC Line status: on-line
> >Battery Status: charging
> >Remaining battery life: 0%
> >Remaining battery time:  0:00:00
> >Number of batteries: 1
> >Battery 0:
> >        Battery Status: charging
> >        Remaining battery life: 0%
> >        Remaining battery time:  0:00:00
> 
> This is strange behavior.  Your system is never reporting the current 
> battery capacity (cap = 0) even though it reports a reasonable battery 
> status (charging).

Yep. It has always been this way.  

> >Unplugging AC power:
> >
> >batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082
> >batt pass2: min 166 total_min 166 total_cap 0
> >
> >
> >wb at chuck ~: apm
> >APM version: 1.2
> >APM Management: Enabled
> >AC Line status: off-line
> >Battery Status: low
> >Remaining battery life: 0%
> >Remaining battery time:  2:31:00
> >Number of batteries: 1
> >Battery 0:
> >        Battery Status: low
> >        Remaining battery life: 0%
> >        Remaining battery time:  2:31:00
> 
> Again, it does not report a valid cap off power but does report a valid 
> rate of use.
> 
> Did you always have this behavior or was this introduced by my commit?

Been there since a long time. 

-- 
Wilko Bulte				wilko at FreeBSD.org