Date: Fri, 5 Mar 2004 10:24:17 -0800 (PST) From: Nate Lawson <nate@root.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: cvs-src@freebsd.org Subject: Re: cvs commit: src/usr.sbin/acpi/acpiconf acpiconf.c Message-ID: <20040305101907.P30482@root.org> In-Reply-To: <20040304.201932.78712700.imp@bsdimp.com> References: <200403050239.i252dI0u007320@sana.init-main.com> <20040304.201932.78712700.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 4 Mar 2004, M. Warner Losh wrote: > In message: <200403051335.55836.doconnor@gsoft.com.au> > "Daniel O'Connor" <doconnor@gsoft.com.au> writes: > : On Fri, 5 Mar 2004 13:09, Takanori Watanabe wrote: > : > : > apm(8) information is only emulated apm status. > : > The acpiconf -i informations are not available from apm(8) interface. > : > : acpiconf -i doesn't show stuff like battery percentage and estimated run time > : though.. > : > : I have a program which does and I'm going to shoe horn it into acpiconf and > : send diffs if I get some spare time :) > : > : It's seriously neat to see how many Watt's your laptop is using when you > : fiddle with stuff :) > > I have hacked my acpiconf to print more battery information too. I think this is the wrong way to go. Instead of having N separate utilities with their different syntax for N power management systems, we should have one user interface for battery and thermal and the PM system exports data in that defined format. My proposed plan is: * Unified sysctls for battery and thermal (hw.power.XXX) * Make sure both acpi(4) and apm(4) export information through that interface. * Move apm(8) to use those sysctls. * Remove any non-acpi-specific code from acpiconf(8) -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040305101907.P30482>