linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Olof Johansson <olof@lixom.net>,
	Paul Mackerras <paulus@samba.org>, Arnd Bergmann <arnd@arndb.de>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 7/16] powerpc: add support for ps3 platform
Date: Tue, 21 Nov 2006 11:54:28 -0800	[thread overview]
Message-ID: <45635974.7080802@am.sony.com> (raw)
In-Reply-To: <20061121134529.GA18620@lst.de>

Christoph Hellwig wrote:
> On Tue, Nov 21, 2006 at 02:42:30PM +0100, Arnd Bergmann wrote:
>> On Tuesday 21 November 2006 14:22, Christoph Hellwig wrote:
>> > The whole port is hypervisor-specific. ?It should be called ps3hv or
>> > sonyhv (in case the plan for more hardware that's crippled by this
>> > hypervisor) 
>> 
>> The hypervisor has a name, it's called 'lv1', and the port already
>> uses that identifier for the low-level interfaces.
>> If the platform is named after the hypervisor, we should not make up
>> a new name but use the one that is already there.
> 
> Actually that makes even more sense, yes.
> 
>> > ps3 should be left for a bare metal port that people may or may not do 
>> 
>> If there will ever be a native port, that will not need its platform
>> directory but can simply go into into common platforms/cell/ and sysdev
>> directories, with a small file for the ppc_md instance. All the interesting
>> files (page table, iommu, interrupt handling) would be shared with native
>> ports to different hardware.
> 
> I guess so, yes.  We'd still add a CONFIG_PS3 for it to not bloat
> kernels that don't want support.


CONFIG_PS3 is most natural to represent the support in 'platforms/ps3', so
I will use that symbol.


-Geoff

  reply	other threads:[~2006-11-21 19:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 20:02 [PATCH 7/16] powerpc: add support for ps3 platform Geoff Levand
2006-11-10 21:23 ` Olof Johansson
2006-11-14  0:11   ` Geoff Levand
2006-11-15 17:54     ` Christoph Hellwig
2006-11-21  2:50     ` Paul Mackerras
2006-11-21 10:11       ` Arnd Bergmann
2006-11-21 10:15         ` Geert Uytterhoeven
2006-11-21 11:59           ` Paul Mackerras
2006-11-21 13:22             ` Christoph Hellwig
2006-11-21 13:42               ` Arnd Bergmann
2006-11-21 13:45                 ` Christoph Hellwig
2006-11-21 19:54                   ` Geoff Levand [this message]
2006-11-21 19:54                 ` Geoff Levand
2006-11-21 19:54               ` Geoff Levand
2006-11-14 14:25   ` Geoff Levand
2006-11-11 11:21 ` Christoph Hellwig
2006-11-11 11:24   ` Christoph Hellwig
2006-11-11 11:50 ` Arnd Bergmann
2006-11-13  3:29   ` Geoff Levand
2006-11-14 14:00   ` Geoff Levand
2006-11-15 18:04 ` Christoph Hellwig
2006-11-16  1:41   ` Geoff Levand
2006-11-16  2:13     ` Michael Ellerman
2006-11-17  1:31       ` Geoff Levand
2006-11-17  6:41     ` Christoph Hellwig
2006-11-17 22:23       ` Benjamin Herrenschmidt
2006-11-18  2:02       ` Geoff Levand
2006-11-21 21:12       ` Geoff Levand
2006-11-17  0:39   ` Benjamin Herrenschmidt
2006-11-17  1:33     ` Geoff Levand
2006-11-17  1:42       ` Michael Ellerman
2006-11-17  2:04         ` Geoff Levand
2006-11-17  2:19           ` Michael Ellerman
2006-11-17  2:44             ` Geoff Levand
2006-11-16 16:35 ` 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=45635974.7080802@am.sony.com \
    --to=geoffrey.levand@am.sony.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=arnd@arndb.de \
    --cc=hch@lst.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).