mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Wes Felter <wesley@felter.org>, linux-kernel@vger.kernel.org
Subject: Re: em64t speedstep technology not supported in kernel yet?
Date: Fri, 30 Sep 2005 09:04:46 -0400	[thread overview]
Message-ID: <20050930130446.GA15658@redhat.com> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6005DECA92@scsmsx403.amr.corp.intel.com>

On Fri, Sep 30, 2005 at 05:20:03AM -0700, Pallipadi, Venkatesh wrote:
 > 
 > >-----Original Message-----
 > >From: linux-kernel-owner@vger.kernel.org 
 > >[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Wes Felter
 > >Sent: Thursday, September 29, 2005 11:58 AM
 > >To: linux-kernel@vger.kernel.org
 > >Subject: Re: em64t speedstep technology not supported in kernel yet?
 > >
 > >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.
 > 
 > Yes. Make sure speedstep is  supported and enabled in BIOS. Typically,
 > there will be a BIOS config option under CPU section, called Speedstep, 
 > Enhanced Speedstep or EIST or something like that. 

The BIOS tables make no difference at all however to the speedstep-centrino
module  (which in retrospect really should have been speedstep-est or something)
as it has no OP() tables or cpu recognition for Xeons.

		Dave


  reply	other threads:[~2005-09-30 13:05 UTC|newest]

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

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=20050930130446.GA15658@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=wesley@felter.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