From owner-freebsd-acpi@FreeBSD.ORG  Tue Jul 26 19:11:38 2005
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: acpi@freebsd.org
Delivered-To: freebsd-acpi@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 78EA716A41F;
	Tue, 26 Jul 2005 19:11:38 +0000 (GMT) (envelope-from nate@root.org)
Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1F59543D45;
	Tue, 26 Jul 2005 19:11:38 +0000 (GMT) (envelope-from nate@root.org)
Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net
	[67.119.74.222])
	by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6QJBbo5016678
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 26 Jul 2005 12:11:38 -0700
Message-ID: <42E68AE8.2050600@root.org>
Date: Tue, 26 Jul 2005 12:11:36 -0700
From: Nate Lawson <nate@root.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jeremie Le Hen <jeremie@le-hen.org>
References: <d9175cad050723030041dd7387@mail.gmail.com>
	<20050723133819.36efb537.lists@yazzy.org>
	<42E29CAA.1020007@root.org>
	<d9175cad0507232047160cc758@mail.gmail.com>
	<20050724215818.55f951ae.lists@yazzy.org>
	<42E42F10.3030309@root.org>
	<20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org>
	<20050726011943.0abe83a0.lists@yazzy.org>
	<42E5C96C.9060105@root.org>
	<20050726135149.GG1610@obiwan.tataz.chchile.org>
In-Reply-To: <20050726135149.GG1610@obiwan.tataz.chchile.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: acpi@freebsd.org, Marcin Jessa <lists@yazzy.org>,
	freebsd-current@freebsd.org
Subject: Re: acpi battery rework patch
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2005 19:11:38 -0000

Jeremie Le Hen wrote:
> Hi Nate,
> 
> 
>>>- Battery:
>>>hw.acpi.battery.life: 87
>>>hw.acpi.battery.time: 103
>>>hw.acpi.battery.state: 1
>>
>>Completely fine.  Time should be -1 (unknown) while on AC power.  And 
>>state is "discharging" when on battery.
>>
>>
>>>- AC:
>>>hw.acpi.battery.life: 70
>>>hw.acpi.battery.time: -1
>>>hw.acpi.battery.state: 2
>>
>>This is fine.  On AC power and state is charging.
>>
>>
>>>- Battery:
>>>hw.acpi.battery.life: 70
>>>hw.acpi.battery.time: 125
>>>hw.acpi.battery.state: 1
>>
>>Time is valid and state is "discharging".
> 
> 
> Where are these states documented ?  What do you think of the idea of
> using the following as a description for the hw.acpi.battery.state
> sysctl ?
>     "0: battery full, 1: discharging, 2: charging"

Currently in the acpiio.h header.  Changing it to a string is a problem 
since multiple flags can be active at once, i.e. "discharging" + 
"critical".  The apm(8) utility does a good job of parsing these so 
perhaps the same code could be used in the sysctl.

-- 
Nate