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 5F2A4DDF56 for ; Fri, 13 Apr 2007 02:50:18 +1000 (EST) In-Reply-To: <461E5B91.5080101@freescale.com> References: <20070326205145.GA2868@ld0162-tx32.am.freescale.net> <20070326205226.GB2931@ld0162-tx32.am.freescale.net> <17949.47307.827348.233684@cargo.ozlabs.ibm.com> <461E51EA.90600@freescale.com> <5925EF50-5323-4CF3-A145-251068AD9AA0@kernel.crashing.org> <461E5B91.5080101@freescale.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: From: Kumar Gala Subject: Re: [PATCH 2/5] bootwrapper: Add CONFIG_DEVICE_TREE Date: Thu, 12 Apr 2007 11:49:51 -0500 To: Scott Wood Cc: linuxppc-dev@ozlabs.org, Paul Mackerras List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Apr 12, 2007, at 11:17 AM, Scott Wood wrote: > Kumar Gala wrote: >> On Apr 12, 2007, at 10:36 AM, Scott Wood wrote: >>> Paul Mackerras wrote: >>> >>>> Hmmm, I'm not sure that I want to be asked about >>>> CONFIG_DEVICE_TREE on >>>> *all* powerpc platforms... Surely this option should depend on >>>> something that says we're including support for a uBoot-able >>>> platform? >>> >>> >>> That's how I originally had it, but I was asked to make it more >>> general. >>> One non-uboot usage is Mark Greer's "Add Makefile rule to wrap dts >>> file in zImage" patch. >>> >>> What about a CONFIG_WANT_DEVICE_TREE that platforms can select if >>> they >>> want to ask the user for a device tree? >> Wouldn't we want this for all systems that don't have true OF? > > Not if there's a non-OF firmware that doesn't need to go through > the bootwrapper (such as modern u-boot). I guess my intent with asking for the CONFIG_DEVICE_TREE to be more generic was to have it point to a .dts for the board/system in question. The kernel proper wouldn't ever use this, but any other build mechanism could. For example, I might have scripts outside of u-boot/kernel that build my images to flash into a board and they could parse .config to get the location of the .dts to create the dtb and produce my flash images. - k