From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nommos.sslcatacombnetworking.com (nommos.sslcatacombnetworking.com [67.18.224.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id C3F0C67BEF for ; Thu, 3 Aug 2006 05:26:13 +1000 (EST) In-Reply-To: <1154545382.12757.1.camel@weaponx.rchland.ibm.com> References: <1154464346.19994.4.camel@cashmere.sps.mot.com> <1154466094.11069.6.camel@localhost> <20060802003504.GA20439@mag.az.mvista.com> <1154481150.2676.3.camel@vader.jdub.homelinux.org> <528646bc0608012020l11690cf7wbb7d93e6ba6eae90@mail.gmail.com> <20060802182319.GI17652@mag.az.mvista.com> <528646bc0608021121l124cd3e8i14dfdfbf40272193@mail.gmail.com> <20060802184930.GN17652@mag.az.mvista.com> <1154545382.12757.1.camel@weaponx.rchland.ibm.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <636D3933-399D-45AB-9DAF-74AB77ABA5FF@kernel.crashing.org> From: Kumar Gala Subject: Re: RFC: Location for Device Tree Sources? Date: Wed, 2 Aug 2006 14:26:13 -0500 To: Josh Boyer Cc: "linuxppc-dev@ozlabs.org" , Guennadi Liakhovetski List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Aug 2, 2006, at 2:03 PM, Josh Boyer wrote: > On Wed, 2006-08-02 at 11:49 -0700, Mark A. Greer wrote: >> On Wed, Aug 02, 2006 at 12:21:37PM -0600, Grant Likely wrote: >>> On 8/2/06, Mark A. Greer wrote: >>>> On Tue, Aug 01, 2006 at 09:20:52PM -0600, Grant Likely wrote: >>>>> I have to second that opinion. The device tree is absolutely >>>>> integral >>>>> with the rest of the code/drivers needed to support a board. I >>>>> say >>>>> there are stronger arguments for keeping the dts files in the >>>>> kernel >>>>> source than there are for the boot wrapper. >>>> >>>> Well, the dts is no good to you without dtc so do we put dtc in the >>>> kernel source tree too? >>> >>> I don't know; should we include gcc also? >>> >>> :p >> >> Yep, my point. >> >> I don't really have a problem with keeping known working dts files in >> arch/powerpc/boot/dts. Perhaps a 1-1 match with files in >> arch/powerpc/configs? > > I like that idea very much. Actually that's what I thought were were > talking about in the first place. > >> >> It would still be nice to have the dtc source, attach tool source, >> and, >> if useful, a more exhaustive collection of dts files in one place. > > I also think that would be useful. While useful, I doubt its likely to happen. I forsee boards that aren't in the kernel tree having their dts live in their private worlds. Also tools like mkimage that come from u-boot will probably still live with u-boot. - kumar