mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wes Felter <wesley@felter.org>
To: linux-kernel@vger.kernel.org
Subject: Re: em64t speedstep technology not supported in kernel yet?
Date: Thu, 29 Sep 2005 13:58:18 -0500	[thread overview]
Message-ID: <433C394A.7010802@felter.org> (raw)
In-Reply-To: <433C1787.4090001@watson.wustl.edu>

Richard Wohlstadter wrote:
> Hello all,
> 
> We recently had Intel give our company a roadmap presentation where they 
> told us that their enhanced speedstep technology was supported by linux 
> kernels 2.6.9+.  I have since tried to get cpufreq speedstep driver to 
> work with no luck on our em64t Xeon 3.6g processors.  Intel even has a 
> webpage describing the technology and how to get it working at url: 
> http://www.intel.com/cd/ids/developer/asmo-na/eng/195910.htm?prn=Y

I think this is a BIOS problem; the BIOS needs to provide the proper 
ACPI frequency/voltage tables for cpufreq to use. You might want to 
harass your system/motherboard vendor.

Alternately maybe you can find someone who can give you the secret table 
and then you can just hardcode it into the driver.

> The only processor I have had luck with so far is a 32-bit Xeon with the 
> p4-clockmod driver(which does not appear to be present in the x86-64 
> kernel).

Beware that p4-clockmod won't increase the power efficiency of your 
system. (As an aside, clock modulation is so simple that you can do it 
from userspace in a few lines of C if you modprobe msr. This works on 
x86-64.)

Wes Felter - wesley@felter.org



  reply	other threads:[~2005-09-29 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 16:34 Richard Wohlstadter
2005-09-29 18:58 ` Wes Felter [this message]
2005-09-30 12:20 Pallipadi, Venkatesh
2005-09-30 13:04 ` Dave Jones
2005-09-30 13:20 Pallipadi, Venkatesh
2005-09-30 13:25 ` Dave Jones

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=433C394A.7010802@felter.org \
    --to=wesley@felter.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome