From: Adrian Bunk <bunk@fs.tum.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
macro@ds2.pg.gda.pl
Subject: Re: RFC: [2.6 patch] better i386 CPU selection
Date: Sat, 13 Sep 2003 13:13:50 +0200 [thread overview]
Message-ID: <20030913111350.GC27368@fs.tum.de> (raw)
In-Reply-To: <200309131102.h8DB2aoA021591@harpo.it.uu.se>
On Sat, Sep 13, 2003 at 01:02:36PM +0200, Mikael Pettersson wrote:
> On Sat, 13 Sep 2003 01:23:04 +0200, Adrian Bunk <bunk@fs.tum.de> wrote:
> >Considering this, I can simply do the following in my proposal of
> >offering every CPU type to the user?
> >
> >config X86_BAD_APIC
> > bool
> > depends on CPU_586TSC
> > default y
>
> That depends on your semantics for CPU_586TSC.
> If it is required for support of pre-MMX P5s, then yes.
> With the current semantics, where a CPU choice simply
> sets a lower bound, then no.
The intention of my "better i386 CPU selection" patch is that you select
all CPUs you want to support.
The semantics is that e.g. CPU_486 doesn't enable support for Pentiums.
> /Mikael
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-09-13 11:14 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 11:02 RFC: [2.6 patch] better i386 CPU selection Mikael Pettersson
2003-09-13 11:13 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-14 8:55 John Bradford
2003-09-14 8:52 John Bradford
[not found] <viay.6qh.11@gated-at.bofh.it>
[not found] ` <vli4.2Ml.15@gated-at.bofh.it>
[not found] ` <vnjR.5Sn.5@gated-at.bofh.it>
[not found] ` <vnD7.6jK.1@gated-at.bofh.it>
[not found] ` <vnMX.6x0.17@gated-at.bofh.it>
[not found] ` <vqKS.2NP.29@gated-at.bofh.it>
2003-09-14 0:07 ` Andi Kleen
2003-09-14 0:10 ` David Lang
2003-09-13 12:51 Adrian Bunk
2003-09-13 14:20 ` Kevin P. Fleming
2003-09-13 17:10 ` Adrian Bunk
2003-09-13 16:11 ` Dave Jones
2003-09-13 16:41 ` Adrian Bunk
2003-09-13 17:21 ` Dave Jones
2003-09-13 18:22 ` Adrian Bunk
2003-09-13 18:35 ` Dave Jones
2003-09-13 21:52 ` Adrian Bunk
2003-09-13 18:21 ` Jeff Garzik
2003-09-13 18:37 ` Dave Jones
2003-09-13 18:53 ` Jeff Garzik
2003-09-13 20:32 ` Alan Cox
2003-09-13 22:07 ` Adrian Bunk
2003-09-13 22:33 ` Jeff Garzik
2003-09-13 18:47 ` Alan Cox
2003-09-13 11:04 Mikael Pettersson
2003-09-12 21:38 Mikael Pettersson
2003-09-12 23:23 ` Adrian Bunk
2003-09-16 12:42 ` Maciej W. Rozycki
2003-09-12 20:09 Mikael Pettersson
2003-09-12 22:51 ` Adrian Bunk
2003-09-07 21:47 Mikael Pettersson
2003-09-07 21:46 Mikael Pettersson
2003-09-07 21:56 ` Adrian Bunk
2003-09-07 16:47 Mikael Pettersson
2003-09-07 17:43 ` Jamie Lokier
2003-09-07 18:09 ` Alan Cox
2003-09-08 8:17 ` Rogier Wolff
2003-09-08 12:36 ` Alan Cox
2003-09-10 14:17 ` Pavel Machek
2003-09-11 6:28 ` Adrian Bunk
2003-09-11 11:04 ` Dave Jones
2003-09-12 20:41 ` Adrian Bunk
2003-09-11 12:10 ` Maciej W. Rozycki
2003-09-12 19:07 ` Adrian Bunk
2003-09-16 12:34 ` Maciej W. Rozycki
2003-09-11 14:25 ` Alan Cox
2003-09-13 10:37 ` Adrian Bunk
2003-09-07 17:51 ` Adrian Bunk
2003-09-07 11:28 Adrian Bunk
2003-09-07 11:46 ` Jan-Benedict Glaw
2003-09-07 13:17 ` Adrian Bunk
2003-09-07 13:48 ` Jan-Benedict Glaw
2003-09-07 12:42 ` Sam Ravnborg
2003-09-07 12:51 ` Adrian Bunk
2003-09-07 12:42 ` Robert Schwebel
2003-09-07 13:00 ` Adrian Bunk
2003-09-07 13:14 ` Robert Schwebel
2003-09-08 15:26 ` Tom Rini
2003-09-07 17:31 ` Alan Cox
2003-09-07 17:48 ` Robert Schwebel
2003-09-07 18:04 ` Alan Cox
2003-09-07 18:26 ` Robert Schwebel
2003-09-07 19:17 ` Alan Cox
2003-09-07 19:17 ` Alan Cox
2003-09-07 17:25 ` Alan Cox
2003-09-11 6:19 ` Adrian Bunk
2003-09-08 0:46 ` Rusty Russell
2003-09-08 14:29 ` Adrian Bunk
2003-09-09 1:11 ` Rusty Russell
2003-09-11 6:22 ` Adrian Bunk
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=20030913111350.GC27368@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=mikpe@csd.uu.se \
/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.