Re: my dothan didn't work with cpufreq...

[Dominik Brodowski <linux@dominikbrodowski.de>]

> Yeah, I worked that out from a closer reading of the docs.  There really
> doesn't seem to be any non-hacky way to work out which CPU you have, and
> they seem to have non-overlapping specs (ie, you can't run a VID#D part
> with VID#A voltages).  The hacky way to work it out would be to read
> back the MSR and see what freq/voltage pair you have (which would only
> work at max speed).
... but as many systems boot at a lower speed on battery power, I wouldn't
want to do this.

> Seems like a reasonable idea, though it would be nice for Dothan users
> to not have an ACPI dependency. 

However, as "enhanced SpeedStep" is going to be introduced on
desktop CPUs, the problem will increase: the MSR will likely have a
different encoding. See Venkatesh's patches for details. Also, I fear that
as more CPUs support enhanced SpeedStep, the larger
speedstep-centrino.{o,ko} will become.

> +static const struct cpu_id cpu_ids[] = {
> +	[CPU_BANIAS]	= { X86_VENDOR_INTEL,	6,  9, 5 },
> +	[CPU_DOTHAN_A1]	= { X86_VENDOR_INTEL,	6, 13, 1 },
> +	[CPU_DOTHAN_B0]	= { X86_VENDOR_INTEL,	6, 13, 6 },

Hm, I'm unsure whether this is proper CodingStyle... IIRC, much effort was
spent in converting such { }s to include the respective "fields", like
	{ .x86_vendor = X86_VENDOR_INTEL, x86_family = 6 ... 
and so on.

	Dominik