Bug#664813: Please use the ondemand cpufreq governor by default (CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND)
On Wed, Mar 21, 2012 at 05:28:44AM +0000, Ben Hutchings wrote:
> On Tue, 2012-03-20 at 21:17 -0700, Josh Triplett wrote:
> > On Wed, Mar 21, 2012 at 12:32:23AM +0000, Ben Hutchings wrote:
> > > On Tue, Mar 20, 2012 at 05:14:37PM -0700, Josh Triplett wrote:
> > > > Source: linux-2.6
> > > > Severity: wishlist
> > > >
> > > > Current versions of the Linux kernel will load most appropriate cpufreq
> > > > modules automatically (using the new autoloading aliases based on x86
> > > > CPU models and features).
> > >
> > > Sadly that's only in 3.4 and depends on the removal of sysdevs in 3.3.
> > > So we probably won't get it in wheezy.
> >
> > Seems to work fine here with 3.3. 3.4 fixed some issues with it,
> > though.
> >
> > (Does wheezy actually have a sufficiently firm release date to predict
> > a target kernel version at this point?)
> [...]
>
> There is no prediction involved; we already took the decision to use
> Linux 3.2.
Will that decision get revisited if more kernels get released before
wheezy freezes? (Quite frequently I've noticed that a team chooses a
particular upstream version of something for a Debian release, and then
the release takes longer than expected.)
- Josh Triplett
Reply to: