From: Nick Piggin <piggin@cyberone.com.au>
To: John Stoffel <stoffel@lucent.com>
Cc: Adrian Bunk <bunk@fs.tum.de>, Andrew Morton <akpm@osdl.org>,
root@chaos.analogic.com, cliffw@osdl.org, mpm@selenic.com,
linux-kernel@vger.kernel.org
Subject: Re: [1/4] better i386 CPU selection
Date: Tue, 20 Jan 2004 10:42:17 +1100 [thread overview]
Message-ID: <400C6B59.6060409@cyberone.com.au> (raw)
In-Reply-To: <16395.62535.600758.816370@gargle.gargle.HOWL>
John Stoffel wrote:
>>>>>>"Adrian" == Adrian Bunk <bunk@fs.tum.de> writes:
>>>>>>
>
>Adrian> The main effect is that better-i386-cpu-selection.patch makes
>Adrian> it easier for people who configure kernels that should work on
>Adrian> different CPU types. A user (= person compiling his own
>Adrian> kernel) does no longer need any deeper knowledge when
>Adrian> e.g. configuring a kernel that should run on both an Athlon
>Adrian> and a Pentium 4 - he simply selects all CPUs he wants to
>Adrian> support in his kernel.
>
>So a user who will only Run this kernel on a PIII for example, doesn't
>need to select *any* other kernels at all? I think the Kconfig help
>screens need to be redone to make this clear.
>
>I enabled all the sub-processors because I wanted to make sure my
>kernel would boot no matter what. It seems like I don't need that any
>more, right?
>
At the top of the "Processor support" menu there is the line
"Select all processors your kernel should support". That sums
it up pretty well.
I might get your point better if you sent a patch.
next prev parent reply other threads:[~2004-01-19 23:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 5:48 2.6.1-rc1-tiny2 Matt Mackall
2004-01-06 6:33 ` 2.6.1-rc1-tiny2 Nick Piggin
2004-01-06 6:46 ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-06 7:08 ` 2.6.1-rc1-tiny2 Nick Piggin
2004-01-10 0:46 ` 2.6.1-rc1-tiny2 Adrian Bunk
2004-01-10 0:50 ` [0/4] better i386 CPU selection Adrian Bunk
2004-01-10 0:52 ` [1/4] " Adrian Bunk
2004-01-10 11:04 ` Wichert Akkerman
2004-01-11 3:13 ` Adrian Bunk
2004-01-14 20:49 ` [-mm patch] " Adrian Bunk
2004-01-16 19:15 ` [1/4] " cliff white
2004-01-16 19:32 ` Richard B. Johnson
2004-01-17 0:01 ` Andrew Morton
2004-01-17 2:57 ` Adrian Bunk
2004-01-19 15:14 ` John Stoffel
2004-01-19 23:42 ` Nick Piggin [this message]
2004-01-17 2:15 ` Adrian Bunk
2004-01-17 9:13 ` Robert Schwebel
2004-01-20 22:10 ` Adrian Bunk
2004-01-20 22:31 ` Richard B. Johnson
2004-01-20 22:47 ` George Anzinger
2004-01-17 10:01 ` aeriksson
2004-01-10 0:57 ` [2/4] move "struct movsl_mask movsl_mask" to usercopy.c Adrian Bunk
2004-01-10 0:57 ` [3/4] proof of concept: make arch/i386/kernel/cpu/Makefile CPU specific Adrian Bunk
2004-01-10 0:58 ` [4/4] proof of concept: make arch/i386/kernel/cpu/mtrr/Makefile " Adrian Bunk
2004-01-10 22:14 ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-12 2:20 ` 2.6.1-rc1-tiny2 Nick Piggin
2004-01-07 14:06 ` 2.6.1-rc1-tiny2 Jens Axboe
2004-01-07 18:50 ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-07 19:27 ` 2.6.1-rc1-tiny2 Mitchell Blank Jr
2004-01-07 20:10 ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-07 21:41 ` 2.6.1-rc1-tiny2 Trond Myklebust
2004-01-07 21:10 ` 2.6.1-rc1-tiny2 Jens Axboe
2004-01-07 21:30 ` 2.6.1-rc1-tiny2 Matt Mackall
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=400C6B59.6060409@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=cliffw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=root@chaos.analogic.com \
--cc=stoffel@lucent.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