Date: Thu, 6 May 2004 04:01:15 -0500 (CDT) From: Mike Silbersack <silby@silby.com> To: Nate Lawson <nate@root.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica/Osd OsdSynch.csrc/sys/i386/include acpica_machdep.h src/sys/ia64/include acpica_machdep.h src/sys/amd64/include acpica_machdep.h Message-ID: <20040506035840.G811@odysseus.silby.com> In-Reply-To: <20040506034307.M811@odysseus.silby.com> References: <200405052004.i45K4EnF029671@repoman.freebsd.org> <20040505171634.N37631@root.org> <20040506025051.V630@odysseus.silby.com> <20040506034307.M811@odysseus.silby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 May 2004, Mike Silbersack wrote: > Good deal, it works as avertised. I even learned a bit of shell scripting > in the process of writing a simple speed switching script. :) > > Of course, the real question is whether or not it'll actually help battery > life at all; this is a mobile celeron, I suspect that I won't have much of > an impact. Ah well. > > Mike "Silby" Silbersack Gah, except that my experiment in clockswitching made the usb stack mad, so it's constantly priniting "usb0: X scheduling overruns", where X appears to be a number containing one or two bits of entropy per second. I will have to go visit ohci.c with a cluebat when I get a chance. Er, it stopped when I plugged in the power cord, and starts again when I unplugged it. Is it possible that ohci.c is reading some USB voltage value instead of the overrun bit that it thinks it is reading? Mike "Silby" Silbersack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040506035840.G811>