From: "Phil Endecott" <phil_wueww_endecott@chezphil.org>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: [PATCH] Mention Intel Atom in Kconfig.cpu
Date: Mon, 13 Oct 2008 11:58:26 +0100 [thread overview]
Message-ID: <1223895506638@dmwebmail.dmwebmail.chezphil.org> (raw)
Am I right in thinking that CONFIG_MCORE2 is the correct choice for an
Intel Atom? (It seems to work for me, so far.) If this is true, since
there are quite a lot of these chips in circulation now and the choice
is not obvious, I think it would be helpful to add something along the
following lines to arch/x86/Kconfig.cpu.
Signed-off-by: Phil Endecott <kconfigcpu@chezphil.org>
---
diff --git a/arch/x86/Kconfig.cpu b/arch/x86/Kconfig.cpu
index b225219..7df0801 100644
--- a/arch/x86/Kconfig.cpu
+++ b/arch/x86/Kconfig.cpu
@@ -263,11 +263,12 @@ config MPSC
in /proc/cpuinfo. Family 15 is an older Xeon, Family 6 a
newer one.
config MCORE2
- bool "Core 2/newer Xeon"
+ bool "Core 2/newer Xeon/Atom"
help
- Select this for Intel Core 2 and newer Core 2 Xeons (Xeon
51xx and 53xx)
- CPUs. You can distinguish newer from older Xeons by the CPU family
- in /proc/cpuinfo. Newer ones have 6 and older ones 15 (not a typo)
+ Select this for Intel Core 2, newer Core 2 Xeon (Xeon 51xx
and 53xx)
+ and Intel Atom CPUs. You can distinguish newer from older
Xeons by
+ the CPU family in /proc/cpuinfo. Newer ones have 6 and older
ones 15
+ (not a typo).
config GENERIC_CPU
bool "Generic-x86-64"
next reply other threads:[~2008-10-13 11:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 10:58 Phil Endecott [this message]
2008-10-13 12:13 ` [PATCH] Mention Intel Atom in Kconfig.cpu (less garbled this time) Phil Endecott
2008-10-13 15:36 ` J.A. Magallón
2008-10-13 12:28 ` [PATCH] Mention Intel Atom in Kconfig.cpu Andi Kleen
2008-10-13 13:18 ` Arjan van de Ven
2008-10-13 13:30 ` Andi Kleen
2008-10-13 13:30 ` Arjan van de Ven
2008-10-13 13:53 ` Andi Kleen
2008-10-13 14:02 ` Adrian Bunk
2008-10-13 14:17 ` Arjan van de Ven
2008-10-13 19:22 ` Phil Endecott
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=1223895506638@dmwebmail.dmwebmail.chezphil.org \
--to=phil_wueww_endecott@chezphil.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox