android.doshaska.net

Attached is the source (GPL) of the overclock module adapted to the Milestone 2.6.32 test kernel. (The already compiled module is included in the zip too.)

Maybe someone will have an idea what all the data added by Motorola to the mpu_opps struct mean...

When used, there's no need to specify the omap2_clk_init_cpufreq_table_addr or mpu_opps_addr/freq_table_addr addresses. The values correct for this particular kernel are used by default. The kernel is compiled without CPUfreq stats, btw...

My note about the changes in the new kernel on the overclock project page: http://code.google.com/p/milestone-overclock/issues/detail?id=54
Module compilation: http://forum.xda-developers.com/showthread.php?t=811132

This is an adaptation of the new CPUfreq interactive governor, backported as module for the 2.6.29 kernel (with Milestone specific defaults).

From governors.txt:
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a workqueue context, the 'interactive' governor does this in a timer context, which gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.

link: milestone-overclock

UPDATE: Hmm, it looks like the the stats are still broken in Tiago's version. I will look at the his sources and try to find what's wrong. Till that time, better use the module version that is attached here.
UPDATE 27 August, 2010: the patch has been incorporated in the new 1.4 version of the milestone-overclock module by tiagosousa, therefore this modified version is no longer needed.

This patch fixes two issues of the original overclock module (v1.2):
1. broken CPUfreq statistics
2. freq_table_addr and mpu_opps_addr not set by echo to /proc/overclock/omap2_clk_init_cpufreq_table_addr (Issue 30)

link: milestone-overclock

If you want to use the CPUfreq "conservative" governor as an alternative to the default "ondemand" governor, attached is the compiled kernel module (from Motorola sources).

From the kernel documentation:
The CPUfreq governor "conservative", much like the "ondemand" governor, sets the CPU depending on the current usage. It differs in behaviour in that it gracefully increases and decreases the CPU speed rather than jumping to max speed the moment there is any load on the CPU. This behaviour is more suitable in a battery powered environment.