cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wouter Verhelst <wouter@grep.be>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: p4-clockmod doesn't seem to allow the highest possible speed
Date: Sat, 10 Jan 2004 20:35:26 +0100	[thread overview]
Message-ID: <20040110193526.GM10531@grep.be> (raw)
In-Reply-To: <20040110185308.GZ14031@poupinou.org>

On Sat, Jan 10, 2004 at 07:53:08PM +0100, Ducrot Bruno wrote:
> On Sat, Jan 10, 2004 at 05:32:12PM +0100, Wouter Verhelst wrote:
> > On Sat, Jan 10, 2004 at 04:41:10PM +0100, Dominik Brodowski wrote:
> > > Unfortunately, you're right. VIA doesn't publish their spec sheets
> > > as Intel does, so there's no speedstep-via driver (yet). Maybe
> > > acpi.ko works?
> > 
> > It does, but when my CPU is throttled, it makes an uncomfortable
> > sound at high frequency, so I try to avoid that.
> 
> Do you mean the processor is at high speed (performance), and throttling
> is enabled?
> 
> So it should not be even surprising.
> 
> The P4 is able to throttle itself, so I guess the throttling
> things done externally by the south bridge would have not even
> been tested by the platform designer...

Uh, I'm not entirely sure I understand what you mean here. The issue is:
when I put the processor in some other T-state than T0, it makes noise.
That happens both when it's in P0 or P1.

Not that it matters -- p4-clockmod seems to do it right :)

-- 
Wouter Verhelst
Debian GNU/Linux -- http://www.debian.org
Nederlandstalige Linux-documentatie -- http://nl.linux.org
"Stop breathing down my neck." "My breathing is merely a simulation."
"So is my neck, stop it anyway!"
  -- Voyager's EMH versus the Prometheus' EMH, stardate 51462.

  reply	other threads:[~2004-01-10 19:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 18:18 p4-clockmod doesn't seem to allow the highest possible speed Wouter Verhelst
2004-01-10 10:15 ` Dominik Brodowski
2004-01-10 11:08   ` Wouter Verhelst
2004-01-10 13:18     ` Dominik Brodowski
2004-01-10 15:02       ` Wouter Verhelst
2004-01-10 15:38         ` Dominik Brodowski
2004-01-10 16:30           ` Wouter Verhelst
2004-01-10 15:21       ` Wouter Verhelst
2004-01-10 15:41         ` Dominik Brodowski
2004-01-10 16:32           ` Wouter Verhelst
2004-01-10 18:53             ` Ducrot Bruno
2004-01-10 19:35               ` Wouter Verhelst [this message]
2004-01-11 15:48                 ` Ducrot Bruno
2004-01-11 17:30                   ` Dominik Brodowski
2004-01-11 18:05                     ` Ducrot Bruno
2004-01-11 17:35                 ` Dominik Brodowski
2004-01-11 19:56                   ` Wouter Verhelst
2004-01-11 20:06                     ` Dominik Brodowski
2004-01-11 20:24                       ` Wouter Verhelst
2004-01-12 12:26                     ` 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=20040110193526.GM10531@grep.be \
    --to=wouter@grep.be \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ducrot@poupinou.org \
    /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