From owner-cvs-all@FreeBSD.ORG Mon Mar 8 12:39:31 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 803F116A4CE; Mon, 8 Mar 2004 12:39:31 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1AFE43D39; Mon, 8 Mar 2004 12:39:30 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i28KdTkj056875; Mon, 8 Mar 2004 13:39:30 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 08 Mar 2004 13:39:32 -0700 (MST) Message-Id: <20040308.133932.45155592.imp@bsdimp.com> To: jhb@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200403081501.55307.jhb@FreeBSD.org> References: <20040305.113544.68047468.imp@bsdimp.com> <200403061118.32829.doconnor@gsoft.com.au> <200403081501.55307.jhb@FreeBSD.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: src-committers@FreeBSD.org cc: nate@root.org cc: cvs-all@FreeBSD.org cc: cvs-src@FreeBSD.org cc: takawata@init-main.com Subject: Re: cvs commit: src/usr.sbin/acpi/acpiconf acpiconf.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2004 20:39:31 -0000 In message: <200403081501.55307.jhb@FreeBSD.org> John Baldwin 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