From: Woody Suwalski <woody@suwalski.net>
To: cpufreq@lists.linux.org.uk
Subject: Processor 6 model 0x16
Date: Sat, 02 Feb 2008 14:52:54 -0500 [thread overview]
Message-ID: <47A4CA16.3040802@suwalski.net> (raw)
Howdy, I have recently got a prototype MB from ASUS with the unsupported
processor (probably new ;-) ).
Printk's at the beginning of cpufreq_p4_get_frequency function show
x86=0x06 and x86_model=0x16.
The processor is unmarked, but looks similar to current PentiumM
processors (but then maybe all processors are packaged same way?)
What would be the safe(est) sequence of tests: say start with case 0x09
AND 0x16
or skip Banias and try Dothan to start?
Or no point - all current Intel stuf should be more or less Core comaptible?
Thanks, Woody Suwalski
Ottawa
PS. The board is in the office, so I can not give you more details till
Monday...
static unsigned int cpufreq_p4_get_frequency(struct cpuinfo_x86 *c)
{
if (c->x86 == 0x06) {
if (cpu_has(c, X86_FEATURE_EST))
printk(KERN_WARNING PFX "Warning: EST-capable
CPU detected. "
"The acpi-cpufreq module offers voltage
scaling"
" in addition of frequency scaling. You
should use "
"that instead of p4-clockmod, if
possible.\n");
switch (c->x86_model) {
case 0x0E: /* Core */
case 0x0F: /* Core Duo */
p4clockmod_driver.flags |= CPUFREQ_CONST_LOOPS;
return
speedstep_get_processor_frequency(SPEEDSTEP_PROCESSOR_PCORE);
case 0x0D: /* Pentium M (Dothan) */
p4clockmod_driver.flags |= CPUFREQ_CONST_LOOPS;
/* fall through */
case 0x09: /* Pentium M (Banias) */
return
speedstep_get_processor_frequency(SPEEDSTEP_PROCESSOR_PM);
}
}
if (c->x86 != 0xF) {
printk(KERN_WARNING PFX "Unknown p4-clockmod-capable
CPU. Please
send an e-mail to <cpufreq@lists.linux.org.uk>\n");
return 0;
}
reply other threads:[~2008-02-02 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47A4CA16.3040802@suwalski.net \
--to=woody@suwalski.net \
--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