From: Dominik Brodowski <linux@brodo.de>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: torvalds@transmeta.com, cpufreq@www.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [2.5. PATCH] cpufreq: correct initialization on Intel Copperm ines
Date: Sun, 10 Nov 2002 10:27:34 +0100 [thread overview]
Message-ID: <20021110102733.A1029@brodo.de> (raw)
In-Reply-To: <A46BBDB345A7D5118EC90002A5072C7807B7E080@orsmsx116.jf.intel.com>; from inaky.perez-gonzalez@intel.com on Sat, Nov 09, 2002 at 04:54:27PM -0800
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
next prev parent reply other threads:[~2002-11-10 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-11 20:42 Perez-Gonzalez, Inaky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021110102733.A1029@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.