From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sunset.davemloft.net (unknown [74.93.104.97]) by ozlabs.org (Postfix) with ESMTP id 2F6B0DDF41 for ; Thu, 12 Apr 2007 16:25:51 +1000 (EST) Date: Wed, 11 Apr 2007 23:25:45 -0700 (PDT) Message-Id: <20070411.232545.45203999.davem@davemloft.net> To: benh@kernel.crashing.org Subject: Re: [PATCH] Start split out of common open firmware code From: David Miller In-Reply-To: <1176357020.8061.123.camel@localhost.localdomain> References: <20070412141905.6f30efd3.sfr@canb.auug.org.au> <20070412153424.bf3957f4.sfr@canb.auug.org.au> <1176357020.8061.123.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Cc: sfr@canb.auug.org.au, paulus@samba.org, linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Benjamin Herrenschmidt Date: Thu, 12 Apr 2007 15:50:20 +1000 > On Thu, 2007-04-12 at 15:34 +1000, Stephen Rothwell wrote: > > This creates kernel/openfw.c (depending on CONFIG_OPENFW) and puts the > > first trivially common bits from the prom.c files into it. > > Is this the right place ? > > I want to split flat DT from live DT in separate files, then we have > of_device.c and of_platform.c that will need merging too, and possibly > the filesystem... that's a lot to put in kernel/ We could make drivers/openfw/{device,platform}.c, maybe that would work best?