From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: In-Reply-To: <1192514455.19073.27.camel@pasglop> References: <20071016050217.GA9052@localhost.localdomain> <18196.20112.728499.256646@cargo.ozlabs.ibm.com> <1192514455.19073.27.camel@pasglop> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <923CAD71-2E7A-4630-8718-54FA96886117@kernel.crashing.org> From: Kumar Gala Subject: Re: Merge dtc Date: Tue, 16 Oct 2007 01:24:52 -0500 To: benh@kernel.crashing.org Cc: linuxppc-dev@ozlabs.org, Paul Mackerras , David Gibson List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Oct 16, 2007, at 1:00 AM, Benjamin Herrenschmidt wrote: > >> You must have missed the thread where various people where >> complaining >> about how powerpc is the only architecture where they can't build >> kernels without some external tool that they don't have, etc., etc. >> >> We thought about shipping compiled DTBs for various platforms, but >> the >> problem there is that they can't be updated with a patch, so whoever >> commits a patch to the relevant .dts would have to remember to run >> dtc >> and commit the updated .dtb as well, which seems a bit error-prone. >> >> In the end, dtc isn't all that much code. We already have several >> other programs that run on the host in the process of making a >> zImage, >> such as wrapper, hack-coff, and addnote, not to mention the various C >> programs that are part of Kbuild, and unifdef, kallsyms, etc. >> >> So I think there definitely is a precedent for including dtc. > > Note that I just tried to build a 4xx kernel today ... and failed > due to > the lack of mkimage .. > > Another one that we need to either add to the kernel or make the > building of cuImage's optional. I think if we add dtc we add mkimage since its even smaller. - k