All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	cbe-oss-dev@ozlabs.org, Jeremy Kerr <jk@ozlabs.org>
Subject: Re: Time for cell code reshuffle?
Date: Sun, 23 Dec 2007 08:00:14 +1100	[thread overview]
Message-ID: <1198357215.6686.8.camel@pasglop> (raw)
In-Reply-To: <200712212015.45088.arnd@arndb.de>


On Fri, 2007-12-21 at 20:15 +0100, Arnd Bergmann wrote:
> > It seems platforms/cell should have the shared and/or generic code,
> and the other
> > stuff moved into a new platform directory, but is it worth the
> effort? 
> 
> There is very little code in platforms/cell that can not be generic,
> so I think
> it's not worth splitting it. The only IBM blade specific files are
> cbe_cpufreq_pmi.c and parts of setup.c and pervasive.c. Everything
> else could
> be shared by about any generic implementation without a hypervisor.

Another option is to have:

platforms/celleb -> platforms/beat

and withing platforms/cell, rename blade specific files to
something (can't find what, works on CAB too) and add celleb
"bare metal" files.

A platform directly doesn't have to deal with one platform. For example,
platforms/44x contains a lot of board support.

Now, one question is how far can we merge celleb support with the common
blade/CAB code...

Cheers,
Ben.

  reply	other threads:[~2007-12-22 21:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 14:22 Time for cell code reshuffle? Arnd Bergmann
2007-12-21 17:23 ` Geoff Levand
2007-12-21 19:15   ` Arnd Bergmann
2007-12-22 21:00     ` Benjamin Herrenschmidt [this message]
2007-12-26 11:42       ` Ishizaki Kou
2007-12-26 22:32         ` Arnd Bergmann
2007-12-22 20:58   ` Benjamin Herrenschmidt
2007-12-22 21:11     ` Josh Boyer
2007-12-22 21:21       ` Benjamin Herrenschmidt
2007-12-22 20:57 ` Benjamin Herrenschmidt
2007-12-23  3:47 ` [Cbe-oss-dev] " Jeremy Kerr
2007-12-23 12:35   ` Christoph Hellwig
2007-12-23 14:06     ` Geert Uytterhoeven
2007-12-23 17:14       ` Luca Barbato

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=1198357215.6686.8.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=jk@ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.