From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <tom_gall@vnet.ibm.com>, <linuxppc-dev@lists.linuxppc.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: CONFIG_ALL_PPC
Date: Wed, 28 Nov 2001 23:19:28 +0100 [thread overview]
Message-ID: <20011128221928.8366@smtp.wanadoo.fr> (raw)
In-Reply-To: <3C0561FE.80489F5E@vnet.ibm.com>
>Hmmm well not that I object because I don't... but I am working on this POP
>board here and technically speaking it's the next in the great PREP / PMAC /
>CHRP chain...
>
>CONFIG_PREP_PMAC_CHRP_POP? ICK!
>
>I'm hopeful in the end it'll fall into the CHRP catagory but some of these
>firmware differences could be a bear to resolve. But I might be a little
>over-alarmist too...
It's a difficult choice ;)
What about CONFIG_COMMON_PPC ? Still a bit misleading, but probably
better than CONFIG_ALL_PPC...
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-28 22:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 22:07 CONFIG_ALL_PPC Paul Mackerras
2001-11-28 22:15 ` CONFIG_ALL_PPC Tom Gall
2001-11-28 22:19 ` Benjamin Herrenschmidt [this message]
2001-11-28 23:34 ` CONFIG_ALL_PPC Paul Mackerras
2001-11-29 0:19 ` CONFIG_ALL_PPC Olaf Hering
2001-12-03 11:45 ` CONFIG_ALL_PPC Olaf Hering
2001-11-28 22:28 ` CONFIG_ALL_PPC Timothy A. Seufert
2001-11-29 8:26 ` CONFIG_ALL_PPC Geert Uytterhoeven
2001-11-29 17:05 ` CONFIG_ALL_PPC Tom Gall
2001-11-28 22:20 ` CONFIG_ALL_PPC Troy Benjegerdes
2001-11-28 22:29 ` CONFIG_ALL_PPC Tom Gall
2001-11-28 22:30 ` CONFIG_ALL_PPC Anton Blanchard
2001-11-28 23:30 ` CONFIG_ALL_PPC Michel Dänzer
2001-11-28 23:43 ` CONFIG_ALL_PPC Tom Rini
2001-11-29 8:36 ` CONFIG_ALL_PPC Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2000-04-23 11:42 CONFIG_ALL_PPC Brad Parker
2000-04-23 18:50 ` CONFIG_ALL_PPC Dan Malek
2000-04-23 19:56 ` CONFIG_ALL_PPC Gabriel Paubert
2000-04-23 20:00 ` CONFIG_ALL_PPC 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=20011128221928.8366@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=tom_gall@vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).