On Mon, 2007-02-05 at 19:30 +0100, Johannes Berg wrote:

The original code here is wrong, it applies "previous" knowledge.
The way the cpufreq core is designed is that the policy for the
secondary CPU that comes online says that it must in fact not
use this policy but use the same as the other CPUs that are
listed, which in fact is CPU#0.

Not tested yet but from what Jacob said this should work.

Works great, will resend with proper signed-off-by etc. Thanks again
Jacob for explaining how it should work.

johannes