public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Murali N Iyer <mniyer@us.ibm.com>
Cc: akpm@osdl.org, linux-kernel <linux-kernel@vger.kernel.org>,
	linuxppc64-dev@ozlabs.org, linuxppc64-dev-bounces@ozlabs.org,
	Paul Mackerras <paulus@samba.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH,RFC] Move Cell platform code to arch/powerpc
Date: Thu, 1 Sep 2005 17:00:17 +0200	[thread overview]
Message-ID: <200509011700.20759.arnd@arndb.de> (raw)
In-Reply-To: <OF16E84E87.433792E2-ON8625706F.001777A1-8625706F.00180C3A@us.ibm.com>

On Dunnersdag 01 September 2005 06:22, Murali N Iyer wrote:
> Architecture "cell" seems to be fine. What is your thought on supporting
> multiple different hardware configurations under cell. I think this patch
> has been tested only in CPBW hardware.  For example "+++

My general idea about future Cell based products is that we make the
changes to the platform code at the time we add new code. Of course,
a number of companies are working on designs that I have no insight in,
so I'll just wait what comes, but at least I've tried to make it
easy to add the stuff that I know about.

> linux-cg/arch/ppc64/kernel/bpa_nvram.c" assumes one particular hardware
> which may not be true for different hardware configurations.

Yes, this one is a bit odd. On the one hand, it is very generic and could
be used for any future open firmware or flat device tree based system
(even non-PowerPC). On the other hand, it works only on one particular
board design currently.

I don't really care about where this is put, ranging from:

arch/{ppc64,powerpc}/kernel/of_nvram.c, meaning that everyone using the
	flat device tree can just add an "nvram" node that will work with
	this driver.

arch/powerpc/platforms/cell/cellblade_nvram.c, to keep it specific to
	the one design that we have, assuming that future Cell based
	designs will use something else.

	Arnd <><

       reply	other threads:[~2005-09-01 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF16E84E87.433792E2-ON8625706F.001777A1-8625706F.00180C3A@us.ibm.com>
2005-09-01 15:00 ` Arnd Bergmann [this message]
2005-09-01  0:47 [PATCH,RFC] Move Cell platform code to arch/powerpc Arnd Bergmann
2005-09-01 14:11 ` Kumar Gala
2005-09-01 15:40   ` Arnd Bergmann

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=200509011700.20759.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev-bounces@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=mniyer@us.ibm.com \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    /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