cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: A van Staalduijnen <cpufreq@toptracker.com>
To: cpufreq@lists.linux.org.uk
Subject: Chipset dependant?
Date: Sat, 12 Aug 2006 00:14:10 +0200	[thread overview]
Message-ID: <44DD0132.8040205@toptracker.com> (raw)

At home I am running an old desktop 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 it's frequency.

I wonder though if it would suffice to turn the cpu into a 'mobile', or 
if it would require to have a different chipset on the motherboard as well.

Any chance cpufreq will work after modding the CPU on this motherboard, 
or would it be useless?


Thanks,

Arjan

             reply	other threads:[~2006-08-11 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 22:14 A van Staalduijnen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-11 15:21 chipset dependant? A van Staalduijnen
2006-08-11 23:21 ` Dave Jones
2006-08-12  8:49 ` Erik Slagter

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=44DD0132.8040205@toptracker.com \
    --to=cpufreq@toptracker.com \
    --cc=cpufreq@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox