From: Tom Rini <trini@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Linus Torvalds <torvalds@osdl.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] raid6: altivec support
Date: Thu, 20 Jan 2005 10:55:38 -0700 [thread overview]
Message-ID: <20050120175537.GB32020@smtp.west.cox.net> (raw)
In-Reply-To: <16878.11077.556326.769738@cargo.ozlabs.ibm.com>
On Wed, Jan 19, 2005 at 08:41:25PM +1100, Paul Mackerras wrote:
> David Woodhouse writes:
>
> > Yeah.... I'm increasingly tempted to merge ppc32/ppc64 into one arch
> > like mips/parisc/s390. Or would that get vetoed on the basis that we
> > don't have all that horrid non-OF platform support in ppc64 yet, and
> > we're still kidding ourselves that all those embedded vendors will
> > either not notice ppc64 or will use OF?
>
> I'm going to insist that every new ppc64 platform supplies a device
> tree. They don't have to have OF but they do need to have the booter
> or wrapper supply a flattened device tree (which is just a few kB of
> binary data as far as the booter/wrapper is concerned). It doesn't
> have to include all the
*shurg*
It really is a great idea, but I think it will just move the ire from
(serial infos, IRQ table, ?) being in platforms/fooboard.[ch] to
platforms/fooboard.h or platforms/fooboard_bootinfos.h
So lets just hope ppc64 keeps getting ignored :)
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-01-20 17:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501082324.j08NOIva030415@hera.kernel.org>
2005-01-09 15:13 ` [PATCH] raid6: altivec support Olaf Hering
2005-01-17 10:16 ` David Woodhouse
2005-01-17 14:58 ` Kumar Gala
2005-01-19 4:11 ` Benjamin Herrenschmidt
2005-01-19 7:43 ` David Woodhouse
2005-01-19 9:41 ` Paul Mackerras
2005-01-20 17:55 ` Tom Rini [this message]
2005-01-19 14:45 ` Kumar Gala
2005-01-19 14:48 ` David Woodhouse
2005-01-19 14:54 ` Kumar Gala
2005-01-19 15:08 ` Geert Uytterhoeven
2005-01-19 15:15 ` Kumar Gala
2005-01-19 15:27 ` Geert Uytterhoeven
2005-01-19 23:25 ` Benjamin Herrenschmidt
2005-01-20 7:40 ` [Lists-linux-kernel-news] " Jon Masters
2005-01-19 18:07 ` Jon Masters
2005-01-19 23:22 ` Benjamin Herrenschmidt
2005-01-23 11:17 ` Sven Luther
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=20050120175537.GB32020@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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).