From: Andi Kleen <ak@muc.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andi Kleen <ak@muc.de>, Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix CPU Names in Kconfig
Date: Tue, 22 Apr 2003 00:07:15 +0200 [thread overview]
Message-ID: <20030421220715.GA14573@averell> (raw)
In-Reply-To: <1050955686.13841.0.camel@dhcp22.swansea.linux.org.uk>
On Mon, Apr 21, 2003 at 10:08:07PM +0200, Alan Cox wrote:
> On Llu, 2003-04-21 at 21:55, Andi Kleen wrote:
> > OldXeon for the P3 based Xeons is a bit confusing, but we cannot
> > fix the Intel marchitecture here.
>
> "Pentium II/III Xeon" v "Pentium IV Xeon"
>
> At least thats what ebay user seem to use to distinguish 8)
The reason I didn't do it is that it cannot be easily typed
in make oldconfig / make config
(but it probably should offer an numeric menu for these cases I guess...)
Fixed version for Linus.
diff -u linux-2.5.68-gencpu/arch/i386/Kconfig-o linux-2.5.68-gencpu/arch/i386/Kconfig
--- linux-2.5.68-gencpu/arch/i386/Kconfig-o 2003-04-20 21:24:16.000000000 +0200
+++ linux-2.5.68-gencpu/arch/i386/Kconfig 2003-04-22 00:06:44.000000000 +0200
@@ -183,7 +183,7 @@
optimizations.
config MPENTIUMIII
- bool "Pentium-III/Celeron(Coppermine)"
+ bool "Pentium-III/Celeron(Coppermine)/Pentium III Xeon"
help
Select this for Intel chips based on the Pentium-III and
Celeron-Coppermine core. This option enables use of some
@@ -191,7 +191,7 @@
extensions.
config MPENTIUM4
- bool "Pentium-4/Celeron(P4-based)"
+ bool "Pentium-4/Celeron(P4-based)/Pentium IV Xeon"
help
Select this for Intel Pentium 4 chips. This includes both
the Pentium 4 and P4-based Celeron chips. This option
next prev parent reply other threads:[~2003-04-21 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 20:55 [PATCH] Fix CPU Names in Kconfig Andi Kleen
2003-04-21 20:08 ` Alan Cox
2003-04-21 22:07 ` Andi Kleen [this message]
2003-04-22 11:33 ` mikpe
2003-04-21 21:05 ` Linus Torvalds
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=20030421220715.GA14573@averell \
--to=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.