From: "Mark Langsdorf" <mark.langsdorf@amd.com>
To: cpufreq@lists.linux.org.uk
Subject: [PATCH] Minor updates to powernow-k8
Date: Mon, 14 May 2007 16:21:37 -0500 [thread overview]
Message-ID: <4648D2E1.5030802@amd.com> (raw)
I've submitted the following patches before, but they don't
seem to have made it into the tree yet.
Update the processor ID check to support newer RevF Turions
and indicate number of processors and cores more cleanly
in startup messages.
Signed-Off-By: Mark Langsdorf <mark.langsdorf@amd.com>
--- arch/i386/kernel/cpu/cpufreq/powernow-k8.c.old 2007-05-14
16:15:34.000000000 -0500
+++ arch/i386/kernel/cpu/cpufreq/powernow-k8.c 2007-05-14
16:16:11.000000000 -0500
@@ -1330,8 +1330,8 @@ static int __cpuinit powernowk8_init(voi
if (supported_cpus == num_online_cpus()) {
printk(KERN_INFO PFX "Found %d %s "
- "processors (" VERSION ")\n", supported_cpus,
- boot_cpu_data.x86_model_id);
+ "processors (%d cpu cores) (" VERSION ")\n",
supported_cpus/cpu_data[0].booted_cores,
+ boot_cpu_data.x86_model_id, supported_cpus);
return cpufreq_register_driver(&cpufreq_amd64_driver);
}
--- arch/i386/kernel/cpu/cpufreq/powernow-k8.h.old 2007-05-14
16:15:44.000000000 -0500
+++ arch/i386/kernel/cpu/cpufreq/powernow-k8.h 2007-05-14
16:16:43.000000000 -0500
@@ -46,7 +46,7 @@ struct powernow_k8_data {
#define CPUID_XFAM 0x0ff00000 /* extended family */
#define CPUID_XFAM_K8 0
#define CPUID_XMOD 0x000f0000 /* extended model */
-#define CPUID_XMOD_REV_G 0x00060000
+#define CPUID_XMOD_REV_G 0x00080000
#define CPUID_XFAM_10H 0x00100000 /* family 0x10 */
#define CPUID_USE_XFAM_XMOD 0x00000f00
#define CPUID_GET_MAX_CAPABILITIES 0x80000000
next reply other threads:[~2007-05-14 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 21:21 Mark Langsdorf [this message]
2007-05-14 21:53 ` [PATCH] Minor updates to powernow-k8 Dave Jones
2007-05-14 21:55 ` Langsdorf, Mark
2007-05-14 23:04 ` 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=4648D2E1.5030802@amd.com \
--to=mark.langsdorf@amd.com \
--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 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.