From: Dave Jones <davej@redhat.com>
To: Matteo Giordano <ilmalteo@gmail.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Make overclock possible with cpufreq
Date: Sun, 28 May 2006 17:22:39 -0400 [thread overview]
Message-ID: <20060528212239.GB5741@redhat.com> (raw)
In-Reply-To: <6d24915a0605281326j597faae7u49daaf78c962e2db@mail.gmail.com>
On Sun, May 28, 2006 at 10:26:56PM +0200, Matteo Giordano wrote:
> I just subscribed to the list to address this issue (I think it's an
> *issue*).
> I'm not a kernel hacker so I'm just guessing here, even if I searched
> and tried all the afternoon.
> It's not possible to use cpufreq with an overclocked CPU because the
> processor's frequencies are "hardcoded" somewhere (the BIOS or a PSB
> table?).
> So if I push my Athlon 64 3200+ to 2.4GHz the "performance" governor
> will always put it to 2GHz max, causing the overclock to be useless.
>
> Isn't really possible to take the _actual_ frequencies into cpufreq?
It's reliant upon the BIOS tables describing valid frequency/voltage pairs.
Obviously, your BIOS has no knowledge of overclocked values.
There's nothing sane we can do here. The only possible way this could
work would be by having a mechanism to feed such pairs to the driver,
overriding the BIOS.
Patches to do this have been posted to the list in the past, but I'm
not enthusiastic about applying them to the mainline kernel, as the
potential for getting something wrong if you don't know what you're
doing is huge, and this has the possibility of exposing hard-to-track
down bugs.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-05-28 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 20:26 Make overclock possible with cpufreq Matteo Giordano
2006-05-28 21:22 ` Dave Jones [this message]
2006-05-29 14:42 ` Bruno Ducrot
2006-05-29 9:48 ` Philip Lawatsch
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=20060528212239.GB5741@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=ilmalteo@gmail.com \
/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.