public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Schwebel <robert@schwebel.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org,
	Rusty Russell <rusty@rustcorp.com.au>,
	Russell King <rmk@arm.linux.org.uk>
Subject: Re: RFC: [2.6 patch] better i386 CPU selection
Date: Sun, 7 Sep 2003 14:42:51 +0200	[thread overview]
Message-ID: <20030907124251.GC5460@pengutronix.de> (raw)
In-Reply-To: <20030907112813.GQ14436@fs.tum.de>

On Sun, Sep 07, 2003 at 01:28:13PM +0200, Adrian Bunk wrote:
> The patch below tries to implement a better i386 CPU selection.

Did you look at how rmk does CPU selection in the ARM tree? He has
developed a very sophisticated scheme as there are lots of completely
different cpu implementations, using a few cores. It might be an idea to
make the schemes more uniform than they are now. 

> There are two different needs:
> 1. the installation kernel of a distribution should support all CPUs 
>    this distribution supports (perhaps starting with the 386)

Ack. 

> 2. a sysadmin might e.g. want a kernel that support both a Pentium-III
>    and a Pentium 4, but doesn't need to support a 386

Ack. 

3. Embedded forlks might want to make a kernel which has support for
exactly the used processor and nothing more. 

> Changes:
[...]
> - AMD Elan is a different subarch, you can't configure a kernel that 
>   runs on both the AMD Elan and other i386 CPUs

Ack. Same with for example Geode. And the subarchs might have different
implementations, like Elan SC400, Elan SC410, Elan SC520. 

> - @Robert:
>   there were no Elan CFLAGS in arch/i386/Makefile???

That seems to have evolved since I last touched the Elan stuff. The
Elans are more or less 486 cores with some edges, so adding -march=i486
should be ok. 

> - which CPUs exactly need X86_ALIGNMENT_16?

I've just copied that from 486. 

> A 2.6.0-test4-mm5 kernel with this patch applied compiled and bootet on
> my PC.

I could do some tests on an Elan board, but not earlier than end of next
week as I'm out of office for some days...

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hornemannstraße 12,  31137 Hildesheim, Germany
    Phone: +49-5121-28619-0 |  Fax: +49-5121-28619-4

  parent reply	other threads:[~2003-09-07 12:42 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-07 11:28 RFC: [2.6 patch] better i386 CPU selection 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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 21:46 Mikael Pettersson
2003-09-07 21:56 ` Adrian Bunk
2003-09-07 21:47 Mikael Pettersson
2003-09-12 20:09 Mikael Pettersson
2003-09-12 22:51 ` Adrian Bunk
2003-09-12 21:38 Mikael Pettersson
2003-09-12 23:23 ` Adrian Bunk
2003-09-16 12:42 ` Maciej W. Rozycki
2003-09-13 11:02 Mikael Pettersson
2003-09-13 11:13 ` Adrian Bunk
2003-09-13 11:04 Mikael Pettersson
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
     [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-14  8:52 John Bradford
2003-09-14  8:55 John Bradford

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=20030907124251.GC5460@pengutronix.de \
    --to=robert@schwebel.de \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=rusty@rustcorp.com.au \
    /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