From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dominik Brodowski <linux@dominikbrodowski.de>
Subject: Re: [2.6. PATCH] Missing default governor choices
Date: Sun, 29 Aug 2004 14:32:00 +0200
Sender: cpufreq-bounces@www.linux.org.uk
Message-ID: <20040829123200.GA16050@dominikbrodowski.de>
Mime-Version: 1.0
Return-path: <cpufreq-bounces+glkc-cpufreq=gmane.org@www.linux.org.uk>
Content-Disposition: inline
List-Id: <cpufreq.vger.kernel.org>
List-Unsubscribe: <http://www.linux.org.uk/mailman/listinfo/cpufreq>,
	<mailto:cpufreq-request@www.linux.org.uk?subject=unsubscribe>
List-Archive: <http://www.linux.org.uk/mailman/private/cpufreq>
List-Post: <mailto:cpufreq@www.linux.org.uk>
List-Help: <mailto:cpufreq-request@www.linux.org.uk?subject=help>
List-Subscribe: <http://www.linux.org.uk/mailman/listinfo/cpufreq>,
	<mailto:cpufreq-request@www.linux.org.uk?subject=subscribe>
Errors-To: cpufreq-bounces+glkc-cpufreq=gmane.org@www.linux.org.uk
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: goatzilla@gmail.com, cpufreq@www.linux.org.uk

> What's the reason for the powersave governor not being selectable as
> default?

Because it doesn't matter much: 
- performance is available during boot so that CPUs starting up at less than
  100% can be boosted to full performance very soon.
- userspace is available to keep the CPU speed at what it was at boot, and
  to allow existing userspace-based setups to work [it offers an equivalent
  interface compared to the one of the old 2.4. cpufreq interface]

All other settings [including min/max ranges, governor for "continuing" use] can
and should be done by either a startup script and/or a userspace daemon.

	Dominik