Messages in this thread | | | Date | Fri, 17 Jun 2005 12:41:00 +0200 | From | Eric Piel <> | Subject | Re: 2.6.12-rc6 missing commit(s) in cpufreq? |
| |
06/17/2005 12:21 PM, Voluspa wrote/a écrit: > According to: > http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.12-rc6 > > There should be a: > > commit 1206aaac285904e3e3995eecbf4129b6555a8973 > Author: Dave Jones <davej@redhat.com> > Date: Tue May 31 19:03:48 2005 -0700 > > [CPUFREQ] Allow ondemand stepping to be changed by user. > > And when I look at: > http://www.kernel.org/git/?p=linux/kernel/git/davej/cpufreq.git;a=commit;h=1206aaac285904e3e3995eecbf4129b6555a8973 > : > > Problem is that neither a clean 2.6.11 patched with patch-2.6.12-rc6 nor > a full linux-2.6.12-rc6.tar.bz (I just downloaded it) contain that > commit. Yes, it is in linux-2.6.12-rc6, but also "[CPUFREQ] ondemand governor automatic downscaling" which back off this change because it introduce a new algorithm which compute automatically this step to the best value.
The cpufreq tree was going during three months separatetly and then all the commits went inside the Linus's tree at once. It might look strange then, but nothing to worry :-)
: > Even more strange is the other discrepancies in that list, suggesting > other missed commits. Live directory from 2.6.12-rc : > > root:sleipner:/sys/devices/system/cpu/cpu0/cpufreq/ondemand# ls > total 0 > 0 ignore_nice 0 sampling_rate 0 sampling_rate_min > 0 sampling_down_factor 0 sampling_rate_max 0 up_threshold That's what you should see, everything is ok :-)
> > Perhaps this is why I can't get the conservative governor to work at all > (it just sits at the freq at which it was loaded, never going up/down no > matter the load). I think it's completetly unrelated. Probably it's better to discuss about this bug on the cpufreq mailing list: cpufreq@lists.linux.org.uk
Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |