From: Ducrot Bruno <ducrot@poupinou.org>
To: aeriksson2@fastmail.fm
Cc: cpufreq@www.linux.org.uk
Subject: Re: Pentium III (Coppermine) cpufreq support
Date: Thu, 29 Jan 2004 12:35:41 +0100 [thread overview]
Message-ID: <20040129113541.GY25416@poupinou.org> (raw)
In-Reply-To: <20040129085037.77B733FFB@latitude.mynet.no-ip.org>
On Thu, Jan 29, 2004 at 09:50:36AM +0100, aeriksson2@fastmail.fm wrote:
>
> Hi all,
>
> Another PIII(Speedstep)/440BZ owner chiming in...
>
> I've been successful in getting the -smi driver to work (I believe).
> However, I need to apply this patch:
>
> --- ../../cf-2.6/cpufreq/linux/arch/i386/kernel/cpufreq/speedstep-lib.c 2003-08-19 15:38:33.000000000 +0200
> +++ arch/i386/kernel/cpu/cpufreq/speedstep-lib.c 2003-11-10 21:41:12.325084272 +0100
> @@ -200,7 +200,7 @@
> */
> rdmsr(MSR_IA32_PLATFORM_ID, msr_lo, msr_hi);
> dprintk(KERN_DEBUG "cpufreq: Coppermine: MSR_IA32_PLATFORM ID is 0x%x, 0x%x\n", msr_lo, msr_hi);
> - if ((msr_hi & (1<<18)) && (msr_hi & (3<<24))) {
> + if ((msr_hi & (1<<18)) ) {
> if (c->x86_mask == 0x01)
> return SPEEDSTEP_PROCESSOR_PIII_C_EARLY;
> else
>
> Now reading the comment just before these lines, it's
> apparent that this is not the way things are supposed to work.
Well, that the only 'official' info we got from Intel in
order to detect a speedstep capable processor in earlier
PIII coppermine... But they seems to be wrong (and actually
some system do have an early speedstep-capable PIII coppermine
that do not pass this check).
> I've asked for this patch to be considered by the maintainers
> and the decision was not to apply it. I'd be interested in
> other approaches to getting past these lines in the cpu
> detection code which works can be committed.
>
> You may want to check this path yourself. But I wouldn't be
> surprised if doing the Wrong Thing here could fry your box.
> Question:
> Is there any chance that tricking the code into accepting
> the cpu as speedstep-capable, would made the code appear to
> work when observing the behavior from outside but actually
> do no good to the metal? I don't have the hardware here to
> check if the box actually does consume less power when in
> low performance mode.
If you allow a non-speedstep capable processor, and if
you use the speedstep-ich driver, this will likely
freeze the system no matter what.
Cheers,
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-01-29 11:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 5:16 Pentium III (Coppermine) cpufreq support visyz
2004-01-29 9:26 ` Dominik Brodowski
2004-01-29 8:50 ` aeriksson2
2004-01-29 11:35 ` Ducrot Bruno [this message]
2004-01-29 9:31 ` aeriksson
2004-01-29 12:39 ` Ducrot Bruno
2004-01-29 10:40 ` Anders Eriksson
2004-01-29 14:26 ` Ducrot Bruno
2004-01-29 13:18 ` aeriksson2
2004-01-29 16:10 ` Ducrot Bruno
2004-01-29 10:56 ` Ducrot Bruno
2004-01-29 20:47 ` visyz
2004-01-29 10:50 ` Ducrot Bruno
2004-01-29 20:28 ` visyz
2004-01-30 9:25 ` Ducrot Bruno
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=20040129113541.GY25416@poupinou.org \
--to=ducrot@poupinou.org \
--cc=aeriksson2@fastmail.fm \
--cc=cpufreq@www.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox