From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from grelber.thyrsus.com (static-71-162-243-5.phlapa.fios.verizon.net [71.162.243.5]) by ozlabs.org (Postfix) with ESMTP id CCC10DDEDB for ; Thu, 18 Oct 2007 08:09:44 +1000 (EST) From: Rob Landley To: "Grant Likely" Subject: Re: [PATCH 1/2] qemu platform, v2 Date: Wed, 17 Oct 2007 18:09:28 -0500 References: <20071001053326.GA15132@localhost.localdomain> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <200710171809.28922.rob@landley.net> Cc: linuxppc-dev@ozlabs.org, Paul Mackerras , Milton Miller , Christoph Hellwig List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wednesday 17 October 2007 3:28:41 pm Grant Likely wrote: > > Including .dtbs in the kernel tree has a big practical problem: > > they're binary, so can't be patch(1)ed, which makes updating them a > > complete PITA. I note that kconfig includes the lex/yacc output files (blah.c_shipped) so you don't have to have lex and yacc installed to run "menuconfig". It _also_ includes the lex/yacc source which is what you patch and rebuild the _shipped files from when they need to be changed. > > I'm working on merging dtc into the kernel tree instead. > > I'm kind of late to this party; but I have to say I disagree. Most of > us are doing just fine installing the dtc tool (and mkimage tool for > that matter). Cloning it in the kernel tree is just asking for > divergence. Milton Miller has some patches that make a "PPC qemu target" kernel image which doesn't include a device tree, and generates a rom image to boot qemu with which contains a device tree and hands it off to the Linux kernel. If qemu can merge that rom image in its BIOS collection, this approach would meet my immediate needs. > Cheers, > g. Rob -- "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.