> But this won't catch FSB overclocking at all (which nowadays seems the
> most common way of oc-ing, since it does not involve any modifications
> to the CPU other than maybe a better cooler). Or am I missing something?
The overclocking experiment was a side line
> And what exactly does the mul
Alan Cox wrote:
> > [overclocked CPU detection code]
> It doesnt work usefully. The bit we really needed (clock multiplier reading)
> does work so its a case of one won lost one
But this won't catch FSB overclocking at all (which nowadays seems the
most common way of oc-ing, since it does not inv
> noticed that the overclocked CPU detection code was dropped between ac16
> and ac17. Since the changelog did not mention it - was the feature
> dropped intentionally, and if so, why?
It doesnt work usefully. The bit we really needed (clock multiplier reading)
does work so its a case of one won
Hmm, I seem to have missed the changelog posting for ac17. However, I
noticed that the overclocked CPU detection code was dropped between ac16
and ac17. Since the changelog did not mention it - was the feature
dropped intentionally, and if so, why?
Holger
-
To unsubscribe from this list: send the
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
Intermediate diffs are available from
http://www.bzimage.org
(Note that the cmsfs port to 2.4 is a work in progress)
2.4.2-ac18
o Debian has another location for db3 (Marc
5 matches
Mail list logo
