From: Bruno Ducrot <ducrot@poupinou.org>
To: Harald Milz <milz@seneca.muc.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Manual PST settings for "unrecognized CPUs"
Date: Tue, 17 Aug 2004 10:08:26 +0200 [thread overview]
Message-ID: <20040817080826.GC29560@poupinou.org> (raw)
In-Reply-To: <20040817062634.6C2404BE94@nathan.muc.de>
Hi (I'm back from very long vacation ;)
On Tue, Aug 17, 2004 at 08:26:34AM +0200, Harald Milz 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.
Mine is a little bit too old btw, and I guess yours should be used
instead for now..
Cheers,
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-08-17 8:08 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 [this message]
2004-08-19 0:05 ` Harald Milz
2004-08-17 18:30 ` GoatZilla
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=20040817080826.GC29560@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=milz@seneca.muc.de \
/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