cvs commit: src/usr.sbin/acpi/acpiconf acpiconf.c
jhb at FreeBSD.org
Fri Mar 5 14:28:37 PST 2004
On Friday 05 March 2004 01:24 pm, Nate Lawson wrote:
> On Thu, 4 Mar 2004, M. Warner Losh wrote:
> > In message: <200403051335.55836.doconnor at gsoft.com.au>
> > "Daniel O'Connor" <doconnor at 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
> * Move apm(8) to use those sysctls.
> * Remove any non-acpi-specific code from acpiconf(8)
Have a 'battstat' command or some such. I thought about having /dev/battX
devices to do ioctl's on for battery status. Since batteries really are
devices, that might be better than sysctl.
John Baldwin <jhb at FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
More information about the cvs-src