From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
"Michel Dnzer" <daenzerm@student.ethz.ch>
Cc: Tony Mantler <nicoya@apia.dhs.org>,
Tom Rini <trini@kernel.crashing.org>, Dan Malek <dan@netx4.com>,
"linuxppc-dev" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: CONFIG_PPC != Mac
Date: Sun, 30 Jul 2000 17:48:48 +0100 [thread overview]
Message-ID: <200007301648.RAA16700@hyperion.valhalla.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="", Size: 899 bytes --]
On Sun, Jul 30, 2000, Geert Uytterhoeven wrote:
> On Sun, 30 Jul 2000, Michel [iso-8859-1] Dänzer wrote:
>> Geert Uytterhoeven wrote:
>> > The Master PPC Penguin decided to no longer allow to build machine specific
>> > kernels, but treat PowerMac/PReP/MTX/CHRP as one big machine type
>> > (`CONFIG_ALL_PPC').
[snip]
> Personally I'd more like a configuration where you can select whatever you
> want of
>
> - PowerMac (CONFIG_PMAC)
> - PReP (CONFIG_PREP)
> - MTX (CONFIG_MTX)
> - CHRP (CONFIG_CHRP)
> - Gemini (CONFIG_GEMINI)
> - EST8260 (CONFIG_EST8260)
> - APUS (CONFIG_APUS)
>
> with of course some extra logic to prevent illegal combinations.
This would definitely get my vote too. There are too many cases where you
can enable conflicting build options at present - it causes much
frustration.
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-30 16:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-30 16:48 Iain Sandoe [this message]
2000-07-31 23:57 ` CONFIG_PPC != Mac Johnnie Peters
-- strict thread matches above, loose matches on Subject: below --
2000-08-02 0:34 Iain Sandoe
[not found] <00073123123600.00771@enzo.bigblue.local>
2000-07-31 21:43 ` Michael Schmitz
[not found] <4.3.2.7.2.20000731184833.00ce9900@mail.lauterbach.com>
2000-07-31 17:38 ` Michael Schmitz
2000-07-31 20:54 ` Michael Schmitz
2000-07-30 12:17 Iain Sandoe
2000-07-28 23:57 Dan Malek
2000-07-29 16:38 ` Tom Rini
2000-07-29 17:26 ` Tony Mantler
2000-07-29 17:40 ` Dan Malek
2000-07-29 17:56 ` Tony Mantler
2000-07-30 2:24 ` Martin Costabel
2000-07-30 2:40 ` Tony Mantler
2000-07-30 2:59 ` Dan Malek
2000-07-31 12:12 ` Franz Sirl
2000-07-31 13:11 ` Martin Costabel
2000-07-31 13:37 ` Franz Sirl
2000-07-31 14:17 ` Andreas Tobler
[not found] ` <4.3.2.7.2.20000731170153.03508c50@mail.lauterbach.com>
2000-07-31 15:27 ` Andreas Tobler
2000-07-31 16:40 ` Michael Schmitz
2000-07-31 16:29 ` Geert Uytterhoeven
2000-08-02 15:17 ` Dan Malek
2000-07-29 18:12 ` Geert Uytterhoeven
2000-07-30 13:03 ` Michel Dänzer
2000-07-30 14:56 ` Geert Uytterhoeven
2000-07-31 23:22 ` Dan Malek
2000-08-02 12:05 ` Geert Uytterhoeven
2000-08-02 19:56 ` Dan Malek
2000-08-02 20:04 ` Ani Joshi
2000-08-02 21:15 ` Benjamin Herrenschmidt
2000-08-02 22:02 ` Michael Schmitz
2000-08-03 1:22 ` Tom Gall
2000-08-03 9:33 ` Michael Schmitz
2000-08-03 11:30 ` Geert Uytterhoeven
2000-07-29 17:36 ` Dan Malek
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=200007301648.RAA16700@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=daenzerm@student.ethz.ch \
--cc=dan@netx4.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=nicoya@apia.dhs.org \
--cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).