From: "J.A. Magallon" <jamagallon@able.es>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
davej@suse.de
Subject: Re: [PATCH] intel-x86 model config cleanup
Date: Thu, 30 May 2002 00:44:23 +0200 [thread overview]
Message-ID: <20020529224423.GA3174@werewolf.able.es> (raw)
In-Reply-To: <20020529143544.GA2224@werewolf.able.es> <3CF53C03.5040301@mandrakesoft.com> <3CF53C34.2080300@mandrakesoft.com>
On 2002.05.29 Jeff Garzik wrote:
>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.
>
Could this be organized this way ?
CONFIG_VENDOR_ CONFIG_CPU_ CONFIG_M
GENERIC GENERIC_386 386
GENERIC_486 486
GENERIC_586 586
GENERIC_686 686
INTEL INTEL_386 386
INTEL_486 486
INTEL_PENTIUM 586
INTEL_PENTIUMMMX 586
INTEL_PENTIUMPRO 686
INTEL_PENTIUM2 686
INTEL_CELERON2 686
INTEL_PENTIUM3 686
INTEL_CELERON3 686
INTEL_PENTIUM4 686
AMD AMD_386 386
AMD_486 486
AMD_K5 586
AMD_K6 K6
AMD_K6II K6
AMD_K6III K6
AMD_K7 K7
AMD_DURON K7
AMD_ATHLON K7
CYRIX CYRIX_386 386
CYRIX_486 486
CYRIX_586 586
CYRIX_686 686
VIA CYRIX_III 686
TRANSMETA TRANSMETA_CRUSOE ???
NATSEMI NATSEMI_586 586
RISE RISE_586 586
IDT IDT_WINCHIPC6 ???
IDT_WINCHIP2 ???
IDT_WINCHIP2A ???
IDT_WINCHIP3 ???
Then for each model you would define its generic CONFIG_M<arch>, and
the specific features not contained in the generic. And then define
the rest of features based on generic.
The CONFIG_M<arch> would serve as a flag for 'this cpu has all features
of a generic xxx'.
Or if you are worried about namespace pollution these could be named
CONFIG_CPU_VENDOR_, CONFIG_CPU_, CONFIG_CPU_M.
BTW: any more stars in processor vendor/model sky ?
Comments awaited...
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre9-jam1 #1 SMP mié may 29 02:20:48 CEST 2002 i686
next prev parent reply other threads:[~2002-05-29 22:44 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
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 [this message]
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=20020529224423.GA3174@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=jgarzik@mandrakesoft.com \
--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 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.