public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	L.A.van.der.Duim@student.rug.nl, akpm@digeo.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] add explicit Pentium II support
Date: 12 Jan 2003 15:13:52 -0500	[thread overview]
Message-ID: <1042402432.834.70.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0301121125370.14031-100000@home.transmeta.com>

On Sun, 2003-01-12 at 14:26, Linus Torvalds wrote:

> The thing I reacted to was that the P4 entry should include the
> P4-based celerons. I have no idea what those are called, though.
> 
> Anyway, applied.

I was thinking the same thing, but the lame name of the chips held me
back - the new Celerons are also called "Celerons".

Regardless, I updated the comments and I call the new Celerons "P4-based
Celerons" which should be descriptive enough.

Patch is against current BK.

	Robert Love

 arch/i386/Kconfig |   12 +++++++-----
 1 files changed, 7 insertions(+), 5 deletions(-)


diff -urN linux-2.5.56/arch/i386/Kconfig linux/arch/i386/Kconfig
--- linux-2.5.56/arch/i386/Kconfig	2003-01-12 15:05:16.000000000 -0500
+++ linux/arch/i386/Kconfig	2003-01-12 15:10:45.000000000 -0500
@@ -120,7 +120,7 @@
 	  - "Pentium-Pro" for the Intel Pentium Pro.
 	  - "Pentium-II" for the Intel Pentium II or pre-Coppermine Celeron.
 	  - "Pentium-III" for the Intel Pentium III or Coppermine Celeron.
-	  - "Pentium-4" for the Intel Pentium 4.
+	  - "Pentium-4" for the Intel Pentium 4 or P4-based Celeron.
 	  - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
 	  - "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
 	  - "Crusoe" for the Transmeta Crusoe series.
@@ -183,11 +183,13 @@
 	  extensions.
 
 config MPENTIUM4
-	bool "Pentium-4"
+	bool "Pentium-4/Celeron(P4-based)"
 	help
-	  Select this for Intel Pentium 4 chips.  Presently these are
-	  treated almost like Pentium IIIs, but with a different cache
-	  shift.
+	  Select this for Intel Pentium 4 chips.  This includes both
+	  the Pentium 4 proper and P4-based Celeron chips.  This option
+	  enables compile flags optimized for the core, uses the
+	  correct cache shift, and applies any applicable Pentium III
+	  optimizations.
 
 config MK6
 	bool "K6/K6-II/K6-III"




  reply	other threads:[~2003-01-12 20:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12 19:03 [PATCH] add explicit Pentium II support Robert Love
2003-01-12 20:16 ` Alan Cox
2003-01-12 19:26   ` Linus Torvalds
2003-01-12 20:13     ` Robert Love [this message]
2003-01-12 21:20       ` Luuk van der Duim
2003-01-12 20:26         ` Robert Love
2003-01-13 18:46           ` Bill Davidsen
2003-01-13 21:38             ` Mike Dresser
     [not found] <20030112194008$7d7e@gated-at.bofh.it>
     [not found] ` <20030112202011$498d@gated-at.bofh.it>
2003-01-12 20:27   ` Thomas Tonino
2003-01-12 20:28     ` Robert Love

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=1042402432.834.70.camel@phantasy \
    --to=rml@tech9.net \
    --cc=L.A.van.der.Duim@student.rug.nl \
    --cc=akpm@digeo.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox