* RE: [2.5. PATCH] cpufreq: correct initialization on Intel Copperm ines
@ 2002-11-10 0:54 Perez-Gonzalez, Inaky
2002-11-10 9:27 ` Dominik Brodowski
0 siblings, 1 reply; 3+ messages in thread
From: Perez-Gonzalez, Inaky @ 2002-11-10 0:54 UTC (permalink / raw)
To: Dominik Brodowski, torvalds; +Cc: cpufreq, linux-kernel
> [2.5. PATCH] cpufreq: Intel Coppermines -- the saga continues.
>
> The detection process for speedstep-enabled Pentium III Coppermines is
> considered proprietary by Intel. The attempt to detect this
> capability using MSRs failed. So, users need to pass the option
> "speedstep_coppermine=1" to the kernel (boot option or parameter) if
> they own a SpeedStep capable PIII Coppermine processor. Tualatins work
> as before.
Cannot you use ACPI to detect that? AFAIK, if the machine supports it, it is
doable.
Cheers,
Inaky Perez-Gonzalez -- Not speaking for Intel - opinions are my own [or my
fault]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [2.5. PATCH] cpufreq: correct initialization on Intel Copperm ines
2002-11-10 0:54 [2.5. PATCH] cpufreq: correct initialization on Intel Copperm ines Perez-Gonzalez, Inaky
@ 2002-11-10 9:27 ` Dominik Brodowski
0 siblings, 0 replies; 3+ messages in thread
From: Dominik Brodowski @ 2002-11-10 9:27 UTC (permalink / raw)
To: Perez-Gonzalez, Inaky; +Cc: torvalds, cpufreq, linux-kernel
Hi,
On Sat, Nov 09, 2002 at 04:54:27PM -0800, Perez-Gonzalez, Inaky wrote:
> > [2.5. PATCH] cpufreq: Intel Coppermines -- the saga continues.
> >
> > The detection process for speedstep-enabled Pentium III Coppermines is
> > considered proprietary by Intel. The attempt to detect this
> > capability using MSRs failed. So, users need to pass the option
> > "speedstep_coppermine=1" to the kernel (boot option or parameter) if
> > they own a SpeedStep capable PIII Coppermine processor. Tualatins work
> > as before.
>
> Cannot you use ACPI to detect that? AFAIK, if the machine supports it, it is
> doable.
Most PIII Coppermine notebooks only have ACPI 1.x which does not include
"Performance States" - an interface to Intel SpeedStep and other, similar
technologies. And when there is a working "Performance States" support in
ACPI, this itself registered as cpufreq driver and then there's no need for
the legacy speedstep driver. So, no, unfortunately your suggestion doesn't
solve the problem.
Dominik
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: [2.5. PATCH] cpufreq: correct initialization on Intel Copperm ines
@ 2002-11-11 20:42 Perez-Gonzalez, Inaky
0 siblings, 0 replies; 3+ messages in thread
From: Perez-Gonzalez, Inaky @ 2002-11-11 20:42 UTC (permalink / raw)
To: 'Dominik Brodowski'; +Cc: cpufreq, linux-kernel
> > Cannot you use ACPI to detect that? AFAIK, if the machine
> > supports it, it is doable.
>
> Most PIII Coppermine notebooks only have ACPI 1.x which does
> not include
> "Performance States" - an interface to Intel SpeedStep and
> other, similar
> technologies.
Bummer - that was something I did not know; thanks for your clarification -
this was the only sollution I found (without IP concerns) when I was
enquiring how to get the specifications to support performance states.
Thanks,
Inaky Perez-Gonzalez -- Not speaking for Intel - opinions are my own [or my
fault]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-11-11 20:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-11-10 0:54 [2.5. PATCH] cpufreq: correct initialization on Intel Copperm ines Perez-Gonzalez, Inaky
2002-11-10 9:27 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2002-11-11 20:42 Perez-Gonzalez, Inaky
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.