The above has a max clock of 1.6ghz.. It has all the regular features included prior to this release - underclocking when it gets too hot.. various non-cpu overclocks and so on.. and unlike previous kernels.. its pretty damn stable.. I've tried to crash it. I can't.. Help me crash it. Don't help me crash it if you're on 3.1 - because this won't work with 3.1.. Ok? alright then.
#older stuff below
This lovely little kernel has a max of 1.646 (because 1.7ghz will run for about 30 seconds). But it also has been setup to set the max clock to 1.2ghz (temporarily) when temps get above 42 deg C.. For people using setcpu, I do not know if it sets only cpu0 to the desired freq (and presumes cpu1 will follow).. but it seems that you need to set both to the desired freq, otherwise it'll use the higher of scaling_max_freqs (cpu0,cpu1 - thus two scaling_max_freqs) and ignore the value you just set.. doesn't make sense? yeah.. ok..
if you set cpu0 to 1504
then you set cpu1 to 1504
then you set cpu0 to 1000
... scaling_max_freq is set to 1000 for cpu0, yet cpuinfo_cur_freq will show higher than that (under load obviously)..
just based on my experience.
Just because the max is 1646... doesn't mean you should complain when/if its unstable.. Well, you can.. but you really don't have to.
This is for 3.01.. Im not sure I trust 3.1 yet. ..
Here.. this has sys/avp/vde/gpu/pclk and of course cpu, overclocked. I ls'd the modules directory for you and got this..
bcm4329.ko cifs.ko ntfs.ko scsi_wait_scan.ko tun.ko
I don't know what it means.
If you have problems with netarchy's kernel and you don't with this.. You're probably insane and making stuff up...
This not my first compile. I run my own custom kernels on Gtab, xoom, G2, and HD2.. All pretty spicy with the overclocks..
This may cause some incontinence.. only some.. its ok tho. perfectly natural.
this is the first time I've posted any kerzanels..
get your ultra verbose changelog there buster.