From owner-freebsd-current Tue Jan 21 10:12:30 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E99D437B401 for ; Tue, 21 Jan 2003 10:12:29 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id C5D2743F65 for ; Tue, 21 Jan 2003 10:12:25 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 66045 invoked by uid 1000); 21 Jan 2003 18:12:26 -0000 Date: Tue, 21 Jan 2003 10:12:25 -0800 (PST) From: Nate Lawson To: Daniel Holmes Cc: freebsd-current@freebsd.org Subject: Re: acpi_cpu printf In-Reply-To: <200301211554.h0LFsKmX002682@zorkmid.dakcs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 21 Jan 2003, Daniel Holmes wrote: > > + printf("acpi_cpu: throttling enabled, %d steps from 100%% to %d.%d%%, " > > + "currently %d.%d%%\n" > > Personally, rather than 'enabled', how about 'available'? Using the > word enabled might give some newbies fits when they try to figure it > out what it means. It sounds like the throttling is already turned on. I did change it to "available" in -current and got a lot of flak since it is enabled (i.e. changes in power state will affect cpu throttling). The "currently" addition is intended to point out that even though the throttling feature is enabled, the current speed is set to 100% (although that could change in the future). -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message