From: Dave Jones <davej@redhat.com>
To: A van Staalduijnen <cpufreq@toptracker.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: chipset dependant?
Date: Fri, 11 Aug 2006 19:21:48 -0400 [thread overview]
Message-ID: <20060811232148.GA28540@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0608111712290.15701@airraid.toptracker.com>
On Fri, Aug 11, 2006 at 05:21:14PM +0200, A van Staalduijnen wrote:
> At home I am running an old box, running an Athlon XP on the old VIA KT133
> (not KT133A) chipset. Since this box is mostly idle I am considering doing
> the old Athlon bridge hack, to turn the cpu into an Athlon XP-M, thinking
> I could be using cpufreq then, in order dynamically scale frequencies.
>
> I wonder though if it would suffice to turn the cpu into a 'mobile', or if
> it would require a different chipset on the motherboard as well (as for
> Intels)?
>
> Any chance cpufreq will work after modding the CPU, or would it be
> useless?
useless. You have no variable VRM on your motherboard, likely no BIOS tables,
and at best you'll just get a new CPU string in /proc/cpuinfo. At worst,
you'll get a dead cpu.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-08-11 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 15:21 chipset dependant? A van Staalduijnen
2006-08-11 23:21 ` Dave Jones [this message]
2006-08-12 8:49 ` Erik Slagter
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 22:14 Chipset dependant? A van Staalduijnen
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=20060811232148.GA28540@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=cpufreq@toptracker.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.