From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 17:46:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73BD816A41F; Mon, 25 Jul 2005 17:46:08 +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 214C343D46; Mon, 25 Jul 2005 17:46:07 +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 j6PHk6o5002928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Jul 2005 10:46:07 -0700 Message-ID: <42E5255D.7050008@root.org> Date: Mon, 25 Jul 2005 10:46:05 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcin Jessa References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> In-Reply-To: <20050724215818.55f951ae.lists@yazzy.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, Eric Kjeldergaard , freebsd-current@freebsd.org Subject: Re: acpi battery rework patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2005 17:46:08 -0000 On Sun, 24 Jul 2005 12:47:13 +0900 Eric Kjeldergaard wrote: >>Excellent. compiled and appears working. It does however have >>different values than the old system for some of the sysctl variables. >> I get >> >>hw.acpi.battery.life: 98 >>hw.acpi.battery.time: 0 >>hw.acpi.battery.state: 0 >>hw.acpi.battery.units: 1 >>hw.acpi.battery.info_expire: 5 >> >>when plugged in. But used to get time as -1 when plugged in and I >>think state may have been 1 when plugged in before (less sure about >>that than the time). Thanks for the enormous amount of work your >>efforts are very much appreciated, Ok, I have tested and committed a patch that corrects the output for "time". I was able to verify that the behavior should be "unknown" when charging/online rather than "0". I just need Marcin's debug output now from the patch I sent earlier today. Thanks, -- Nate