public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale•com>
To: "Geert Uytterhoeven" <geert@linux-m68k•org>
Cc: 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>,
	"H. Peter Anvin" <hpa@zytor•com>
Subject: Re: [PATCH] raid6: altivec support
Date: Wed, 19 Jan 2005 09:15:23 -0600	[thread overview]
Message-ID: <F0F87817-6A2C-11D9-AC28-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <Pine.GSO.4.61.0501191606260.15516@waterleaf.sonytel.be>


On Jan 19, 2005, at 9:08 AM, Geert Uytterhoeven wrote:

> On Wed, 19 Jan 2005, 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=20
> with 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=20
> broken
> > > in my mind.
> >
> > The binary structure which changes every few weeks and which is=20
> shared
>  > between the bootloader and the kernel? Yeah, "somewhat broken" is=20=

> one
> > way of putting it :)
>  >
> > The ARM kernel does it a lot better with tag,value pairs.
>
> As does m68k... That's why we never got beyond bootinfo major version=20=

> 2.

Out of interest, on ARM & m68k I would assume that the list of tag's=20
gets added to over time?

- kumar

  reply	other threads:[~2005-01-19 15:15 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
2005-01-19 15:08             ` Geert Uytterhoeven
2005-01-19 15:15               ` Kumar Gala [this message]
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=F0F87817-6A2C-11D9-AC28-000393DBC2E8@freescale.com \
    --to=kumar.gala@freescale$(echo .)com \
    --cc=geert@linux-m68k$(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