From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-da0-f48.google.com ([209.85.210.48]:55977 "EHLO mail-da0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757505Ab3BVQAh (ORCPT ); Fri, 22 Feb 2013 11:00:37 -0500 Received: by mail-da0-f48.google.com with SMTP id w4so419753dam.35 for ; Fri, 22 Feb 2013 08:00:37 -0800 (PST) Date: Fri, 22 Feb 2013 08:00:44 -0800 From: Olof Johansson Subject: Re: [RFC] Kbuild support for ARM FIT images Message-ID: <20130222160044.GA16357@quad.lixom.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Joel A Fernandes Cc: u-boot@lists.denx.de, Linux OMAP List , linux-kbuild@vger.kernel.org, Linux ARM Kernel List , "Fernandes, Joel A" , tony@atomide.com, "Rini, Tom" , Grant Likely , Grant Likely On Wed, Feb 20, 2013 at 07:37:10PM -0600, Joel A Fernandes wrote: > Any comments on this approach? Is it better to merge mkfitsrc.sh with > mkuboot.sh? I know this was discussed quite extensively yesterday, but here is my take on it: Given the recent complications from multiplatform, we really saw a strong reason to _not_ do the final boot wrapping in the kernel build system. Produce the zImage and the DTB files, and have a surrounding script that bundles the two in a format that your particular device needs. Most distros have scripts to handle the "make install" step of a kernel build. That's where this belongs, not in the actual build step. -Olof