From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound1-ash-R.bigfish.com (outbound-ash.frontbridge.com [206.16.192.249]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "*.bigfish.com", Issuer "*.bigfish.com" (not verified)) by ozlabs.org (Postfix) with ESMTP id 0C78567D12 for ; Wed, 22 Nov 2006 06:58:53 +1100 (EST) Message-ID: <45635974.7080802@am.sony.com> Date: Tue, 21 Nov 2006 11:54:28 -0800 From: Geoff Levand MIME-Version: 1.0 To: Christoph Hellwig Subject: Re: [PATCH 7/16] powerpc: add support for ps3 platform References: <4554DACB.8060809@am.sony.com> <17762.59947.937875.546225@cargo.ozlabs.ibm.com> <20061121132253.GA17530@lst.de> <200611211442.31667.arnd@arndb.de> <20061121134529.GA18620@lst.de> In-Reply-To: <20061121134529.GA18620@lst.de> Content-Type: text/plain; charset=UTF-8 Cc: Geert Uytterhoeven , Olof Johansson , Paul Mackerras , Arnd Bergmann , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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