From: Geoff Levand <geoffrey.levand@am•sony.com>
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: Fri, 21 Dec 2007 09:23:08 -0800 [thread overview]
Message-ID: <476BF67C.2030405@am.sony.com> (raw)
In-Reply-To: <200712211522.03841.arnd@arndb.de>
Arnd Bergmann wrote:
> We've been discussing in the past a few times where we should best put
> the spufs code, and when to do it. Since Jeremy and I now have all the
> current patches in powerpc.git, maybe we should do it now.
>
> To the question, where what it should go, I'd leave the decision to
> Jeremy, but my current idea would be:
>
> arch/powerpc/platforms/cell/spufs -> arch/powerpc/spufs
> arch/powerpc/platforms/cell/spu_{callbacks,base,syscalls,fault,notify}.[co]
> -> arch/powerpc/spufs/{callbacks,base,syscalls,fault,notify}.[co]
I think we should consider support for SpursEngine. At the moment I have no
idea of what it needs, and if no one else does we need to find out.
> If we do it in git now, that should result in a minimal breakage of patches.
>
> A related question is what to do about the location of the other cell
> related files. platforms/ps3 is already pretty self-contained once we have
> spufs outside of platforms/cell, but there is still some code shared between
> platforms/cell and platforms/celleb, and each of these directories also contains
> code that is only relevant for a subset of the platforms.
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?
-Geoff
next prev parent reply other threads:[~2007-12-21 17:23 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 [this message]
2007-12-21 19:15 ` Arnd Bergmann
2007-12-22 21:00 ` Benjamin Herrenschmidt
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=476BF67C.2030405@am.sony.com \
--to=geoffrey.levand@am$(echo .)sony.com \
--cc=arnd@arndb$(echo .)de \
--cc=cbe-oss-dev@ozlabs$(echo .)org \
--cc=jk@ozlabs$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(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