All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jwilson@redhat.com>
To: "Kwon, Owen" <owen.kwon@intel.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Enabling CPU freq in a new CPU
Date: Tue, 23 Oct 2007 08:44:07 -0400	[thread overview]
Message-ID: <471DEC97.4070705@redhat.com> (raw)
In-Reply-To: <9981749032FE174C9F521A11BDEEBDFC4C4774@jpsmsx411.gar.corp.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 669 bytes --]

Kwon, Owen wrote:
> I am testing speedstep function with newer Intel CPU. Kernel option is
> enabled at compile time, but while booting, CPUID check seemed to fail.
> The message is
> 
> "p4-clockmod : Unknown p4-clockmod-capable CPU ~~~"
> 
> 
> Do I need to implement additional code to test this function? Or is it
> safe to bypass the CPUID check part?
> 
> 
> I don't know this is required, but Kernel version is 2.6.22.

p4-clockmod is for much older p4 processors, and even then, often isn't
recommended for use. What you want for any reasonably new intel
processor is acpi-cpufreq, not p4-clockmod.

-- 
Jarod Wilson
jwilson@redhat.com



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

[-- Attachment #2: Type: text/plain, Size: 147 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq

  reply	other threads:[~2007-10-23 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23  6:04 Enabling CPU freq in a new CPU Kwon, Owen
2007-10-23 12:44 ` Jarod Wilson [this message]
2007-10-24  0:54   ` Kwon, Owen

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=471DEC97.4070705@redhat.com \
    --to=jwilson@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=owen.kwon@intel.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.