From: Kumar Gala <kumar.gala@freescale•com>
To: "David Woodhouse" <dwmw2@infradead•org>
Cc: "H. Peter Anvin" <hpa@zytor•com>,
Linux Kernel list <linux-kernel@vger•kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs•org>,
Linus Torvalds <torvalds@osdl•org>,
Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH] raid6: altivec support
Date: Wed, 19 Jan 2005 08:54:49 -0600 [thread overview]
Message-ID: <115DD72E-6A2A-11D9-AC28-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1106146083.26551.526.camel@hades.cambridge.redhat.com>
On Jan 19, 2005, at 8:48 AM, David Woodhouse wrote:
> On Wed, 2005-01-19 at 08:45 -0600, Kumar Gala wrote:
> > We did talk about looking at using some work Ben did in ppc64 with=20=
> OF
> > in ppc32.=A0 John Masters was looking into this, but I havent heard=20=
> much
> > from him on it lately.
> >
> > The firmware interface on the ppc32 embedded side is some what =
broken
> > in my mind.
>
> The binary structure which changes every few weeks and which is shared
> between the bootloader and the kernel? Yeah, "somewhat broken" is one
> way of putting it :)
>
> The ARM kernel does it a lot better with tag,value pairs.
The funny thing is that one of the variants on ppc32 supports tag,=20
value pairs
- kumar=
next prev parent reply other threads:[~2005-01-19 14:55 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
2005-01-19 14:45 ` Kumar Gala
2005-01-19 14:48 ` David Woodhouse
2005-01-19 14:54 ` Kumar Gala [this message]
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=115DD72E-6A2A-11D9-AC28-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale$(echo .)com \
--cc=dwmw2@infradead$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=torvalds@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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