All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Wohlstadter <rwohlsta@watson.wustl.edu>
To: linux-kernel@vger.kernel.org
Subject: em64t speedstep technology not supported in kernel yet?
Date: Thu, 29 Sep 2005 11:34:15 -0500	[thread overview]
Message-ID: <433C1787.4090001@watson.wustl.edu> (raw)

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 made a bugzilla report to redhat [Bug 169290] and got a reply that 
none of the Xeon's were supported yet on speedstep because they cannot 
find documentation detailing the tables of frequencies these CPUs support.

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).

Anyone have any knowledge regarding cpufreq and when the em64t's are 
going have a linux driver supporting the speedstep technology?  If it is 
an issue of Intel not providing the neccessary info, maybe I can press 
the issue with the gentlemen that came to my office and stated support 
was there already.

Thanks for any info and advice.  Please CC my on any replies since I am 
not on the list.

Rich Wohlstadter
Genome Sequencing Center
Washington Univ. of St. Louis

             reply	other threads:[~2005-09-29 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 16:34 Richard Wohlstadter [this message]
2005-09-29 18:58 ` em64t speedstep technology not supported in kernel yet? Wes Felter
  -- strict thread matches above, loose matches on Subject: below --
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=433C1787.4090001@watson.wustl.edu \
    --to=rwohlsta@watson.wustl.edu \
    --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 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.