cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@poupinou.org>
To: aeriksson@fastmail.fm
Cc: cpufreq@www.linux.org.uk, aeriksson2@fastmail.fm
Subject: Re: Pentium III (Coppermine) cpufreq support
Date: Thu, 29 Jan 2004 13:39:55 +0100	[thread overview]
Message-ID: <20040129123955.GZ25416@poupinou.org> (raw)
In-Reply-To: <20040129093110.5E7FF3F60@latitude.mynet.no-ip.org>

On Thu, Jan 29, 2004 at 10:31:05AM +0100, aeriksson@fastmail.fm wrote:
> 
> > > 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).
> > 
> Sounds promising.
> 
> > > 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.
> > 
> -ich. ? Do you mean -smi? That's the one I use...

And?  This code is shared with *all* speedstep drivers.

> Anyway, I guess I can conclude that i do have a speedstep capable box.
> If we can get feedback from others (e.g. visyz) indicating that this
> test may need to be relaxed/fixed/whatever a bit for different boxes,
> would a CONFIG_CPUFREQ_ANCIENT_SPEEDSTEP patch & option which
> captures that be adopted?

Make sense, but I know that such system already exist...

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2004-01-29 12:39 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
2004-01-29  9:31       ` aeriksson
2004-01-29 12:39         ` Ducrot Bruno [this message]
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=20040129123955.GZ25416@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=aeriksson2@fastmail.fm \
    --cc=aeriksson@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