From owner-cvs-all@FreeBSD.ORG Thu May 6 02:01:18 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 86D3316A4CF for ; Thu, 6 May 2004 02:01:18 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id C1B2E43D58 for ; Thu, 6 May 2004 02:01:17 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 88984 invoked from network); 6 May 2004 09:01:17 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 6 May 2004 09:01:17 -0000 X-pair-Authenticated: 209.68.2.70 Date: Thu, 6 May 2004 04:01:15 -0500 (CDT) From: Mike Silbersack To: Nate Lawson In-Reply-To: <20040506034307.M811@odysseus.silby.com> Message-ID: <20040506035840.G811@odysseus.silby.com> References: <200405052004.i45K4EnF029671@repoman.freebsd.org> <20040505171634.N37631@root.org> <20040506025051.V630@odysseus.silby.com> <20040506034307.M811@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.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 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: Thu, 06 May 2004 09:01:18 -0000 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