From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
davej@suse.de, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] intel-x86 model config cleanup
Date: Wed, 29 May 2002 16:38:12 -0400 [thread overview]
Message-ID: <3CF53C34.2080300@mandrakesoft.com> (raw)
In-Reply-To: <20020529143544.GA2224@werewolf.able.es> <3CF53C03.5040301@mandrakesoft.com>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
Jeff Garzik wrote:
>
> This implies separating the concept of a "generic x86 kernel that
> supports N CPU types" from "kernel supports one CPU type and one
> only." The i386/config.in is currently a mishmash of both. Dave Jones
> did some work along these lines in his "cpuchoice" diff, which I have
> attached.
....or rather, attached here.
[-- Attachment #2: cpu-choice-2.diff --]
[-- Type: text/plain, Size: 2544 bytes --]
diff -urN --exclude-from=/home/davej/.exclude linux/arch/i386/config.in linux-dj/arch/i386/config.in
--- linux/arch/i386/config.in Mon Nov 12 19:58:08 2001
+++ linux-dj/arch/i386/config.in Tue Dec 4 00:40:28 2001
@@ -26,22 +26,75 @@
mainmenu_option next_comment
comment 'Processor type and features'
-choice 'Processor family' \
+choice 'Processor vendor' \
+ "AMD CONFIG_VENDOR_AMD \
+ Cyrix CONFIG_VENDOR_CYRIX \
+ Generic CONFIG_VENDOR_GENERIC \
+ IDT CONFIG_VENDOR_IDT \
+ Intel CONFIG_VENDOR_INTEL \
+ NationalSemiconductor CONFIG_VENDOR_NATSEMI \
+ RiSE CONFIG_VENDOR_RISE \
+ Transmeta CONFIG_VENDOR_TRANSMETA \
+ VIA CONFIG_VENDOR_VIA" Generic
+
+if [ "$CONFIG_VENDOR_AMD" = "y" ]; then
+ choice 'Processor family' \
+ "386 CONFIG_M386 \
+ 486 CONFIG_M486 \
+ K5/5x86 CONFIG_M586 \
+ K6/K6-II/K6-III CONFIG_MK6 \
+ Athlon/Duron CONFIG_MK7" Athlon
+fi
+
+if [ "$CONFIG_VENDOR_CYRIX" = "y" ]; then
+ choice 'Processor family' \
+ "386 CONFIG_M386 \
+ 486 CONFIG_M486 \
+ 586/5x86/6x86/6x86MX CONFIG_M586" 586
+fi
+
+if [ "$CONFIG_VENDOR_GENERIC" = "y" ]; then
+ choice 'Minimum spec CPU to generate code for' \
+ "386 CONFIG_M386 \
+ 486 CONFIG_M486 \
+ 586 CONFIG_M586 \
+ 686 CONFIG_M686" 386
+fi
+
+if [ "$CONFIG_VENDOR_IDT" = "y" ]; then
+ choice 'Processor family' \
+ "Winchip-C6 CONFIG_MWINCHIPC6 \
+ Winchip-2 CONFIG_MWINCHIP2 \
+ Winchip-2A/Winchip-3 CONFIG_MWINCHIP3D" Winchip-C6
+fi
+
+if [ "$CONFIG_VENDOR_INTEL" = "y" ]; then
+ choice 'Processor family' \
"386 CONFIG_M386 \
486 CONFIG_M486 \
- 586/K5/5x86/6x86/6x86MX CONFIG_M586 \
Pentium-Classic CONFIG_M586TSC \
Pentium-MMX CONFIG_M586MMX \
Pentium-Pro/Celeron/Pentium-II CONFIG_M686 \
Pentium-III/Celeron(Coppermine) CONFIG_MPENTIUMIII \
- Pentium-4 CONFIG_MPENTIUM4 \
- K6/K6-II/K6-III CONFIG_MK6 \
- Athlon/Duron/K7 CONFIG_MK7 \
- Crusoe CONFIG_MCRUSOE \
- Winchip-C6 CONFIG_MWINCHIPC6 \
- Winchip-2 CONFIG_MWINCHIP2 \
- Winchip-2A/Winchip-3 CONFIG_MWINCHIP3D \
- CyrixIII/C3 CONFIG_MCYRIXIII" Pentium-Pro
+ Pentium-4 CONFIG_MPENTIUM4" Pentium-Pro
+fi
+
+if [ "$CONFIG_VENDOR_NATSEMI" = "y" ]; then
+ define_bool CONFIG_M586 y
+fi
+
+if [ "$CONFIG_VENDOR_RISE" = "y" ]; then
+ define_bool CONFIG_M586 y
+fi
+
+if [ "$CONFIG_VENDOR_TRANSMETA" = "y" ]; then
+ define_bool CONFIG_MCRUSOE y
+fi
+
+if [ "$CONFIG_VENDOR_VIA" = "y" ]; then
+ define_bool CONFIG_MCYRIXIII y
+fi
+
#
# Define implied options from the CPU selection here
#
next prev parent reply other threads:[~2002-05-29 20:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 14:35 [PATCH] intel-x86 model config cleanup J.A. Magallon
2002-05-29 20:37 ` Jeff Garzik
2002-05-29 20:38 ` Jeff Garzik [this message]
2002-05-29 22:05 ` Albert D. Cahalan
2002-05-30 0:11 ` Dave Jones
2002-05-30 2:43 ` Albert D. Cahalan
2002-05-30 4:34 ` Jeff Garzik
2002-05-30 11:09 ` Dave Jones
2002-05-29 22:44 ` J.A. Magallon
2002-05-29 22:54 ` Jeff Garzik
2002-05-29 23:06 ` J.A. Magallon
2002-05-29 23:12 ` Jeff Garzik
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=3CF53C34.2080300@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=jamagallon@able.es \
--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