All of lore.kernel.org
 help / color / mirror / Atom feed
From: GoatZilla <goatzilla@gmail.com>
To: cpufreq@www.linux.org.uk
Subject: Re: Manual PST settings for "unrecognized CPUs"
Date: Tue, 17 Aug 2004 14:30:00 -0400	[thread overview]
Message-ID: <39e348480408171130537c34e6@mail.gmail.com> (raw)
In-Reply-To: <20040817062634.6C2404BE94@nathan.muc.de>

Ah, I just found your patch back in June; looks like good stuff.  I'll
give it a try when I get Linux onto my machine.

It's odd that you couldn't get below 9x on the multipliers.  With
CPUMSR I was able to take my Duron all the way down to 3x (I
underclocked the FSB as well to 100MHz).  The curious thing was it was
stable at 3x, locked up at 4x, and was stable again at 5x.  I would
think the core voltage that runs the CPU at full speed should be
acceptable at the lower speeds.

As far as the max FID is concerned, you've probably figured it out by
now, but the max FID that can be set by software is controlled by the
L6 bridges on the CPU package.








On Tue, 17 Aug 2004 08:26:34 +0200 (CEST), Harald Milz
<milz@seneca.muc.de> wrote:
> GoatZilla <goatzilla@gmail.com> wrote:
> > I saw a patch fly by a short while ago where a user added some
> > settings for an unrecognized config.  Is this the only way to hack in
> > a PST?
> 
> Actually there were (at least) two patches - Bruno's patch which
> implemented additional /proc fs entries to send frequency settings to, and
> mine which uses command line parameters for the powernow-k7 module. You can
> find them in the ML archive. Internally, they do basically the same thing.
> Mine is a little inferior as far as sanity checks. But It Works For Me
> [TM].
> 
> Please be advised that you _could_ potentially fry your CPU if you use them
> :-) But IMHO it's quite unlikely.
> 
> What these patches can't do is set the VID on most (?) desktop boards
> because of a lack of hardware support. But you should be able to lower the
> FID to a certain extent, and the power consumption is linearly proportional
> to the frequency, after all.
> 
> --
> "Proper Preparation Prevents Poor Performance."
> 
> _______________________________________________
> Cpufreq mailing list
> Cpufreq@www.linux.org.uk
> http://www.linux.org.uk/mailman/listinfo/cpufreq
>

  parent reply	other threads:[~2004-08-17 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 23:13 Manual PST settings for "unrecognized CPUs" GoatZilla
2004-08-17  6:26 ` Harald Milz
2004-08-17  8:08   ` Bruno Ducrot
2004-08-19  0:05     ` Harald Milz
2004-08-17 18:30   ` GoatZilla [this message]
2004-08-19  0:16     ` Harald Milz
2004-08-22  7:12       ` GoatZilla
  -- strict thread matches above, loose matches on Subject: below --
2004-08-17 18:38 Davin Carter
2004-08-19  0:19 ` Harald Milz

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=39e348480408171130537c34e6@mail.gmail.com \
    --to=goatzilla@gmail.com \
    --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 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.