From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw01.freescale.net (az33egw01.freescale.net [192.88.158.102]) by ozlabs.org (Postfix) with ESMTP id 840CD67BEB for ; Thu, 3 Aug 2006 04:23:23 +1000 (EST) Subject: Re: RFC: Location for Device Tree Sources? From: Matthew McClintock To: "Mark A. Greer" In-Reply-To: <20060802182226.GH17652@mag.az.mvista.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> <20060802182226.GH17652@mag.az.mvista.com> Content-Type: text/plain Date: Wed, 02 Aug 2006 13:22:55 -0500 Message-Id: <1154542975.5550.29.camel@localhost> Mime-Version: 1.0 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 Wed, 2006-08-02 at 11:22 -0700, Mark A. Greer wrote: > Well, if you're going to keep prebuilt dtb files there, why wouldn't > you > want the dts that makes that dtb to be in the same place? > One option is the *just* include the working tested DTB files in the kernel source. That way there is a method to boot the boards. If you end user wants to work with a different DTB they can go download the DTS from another source (or optionally derive the DTS from the DTB) and make changes. That way we do not have to include 'dtc' in the kernel, and we still have a valid DTB for every board included in the kernel. Also, there is no reason to include both the DTB and DTS in the kernel considering they can be easily derived from one another using 'dtc' -Matthew