From: Olof Johansson <olof@lixom.net>
To: Joel A Fernandes <agnel.joel@gmail.com>
Cc: u-boot@lists.denx.de,
Linux OMAP List <linux-omap@vger.kernel.org>,
linux-kbuild@vger.kernel.org,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
"Fernandes, Joel A" <joelagnel@ti.com>,
tony@atomide.com, "Rini, Tom" <trini@ti.com>,
Grant Likely <grant.likely@secretlab.ca>,
Grant Likely <glikely@secretlab.ca>
Subject: Re: [RFC] Kbuild support for ARM FIT images
Date: Fri, 22 Feb 2013 08:00:44 -0800 [thread overview]
Message-ID: <20130222160044.GA16357@quad.lixom.net> (raw)
In-Reply-To: <CAD=GYpbF_3uRzhUnV=MwDiy-ekvZKJztJbkhNM0u_pvG-UCw4w@mail.gmail.com>
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
next prev parent reply other threads:[~2013-02-22 16:00 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 1:37 [RFC] Kbuild support for ARM FIT images Joel A Fernandes
2013-02-21 4:26 ` Stephen Warren
2013-02-21 7:15 ` Joel A Fernandes
2013-02-21 18:58 ` Stephen Warren
2013-02-21 19:18 ` Tom Rini
2013-02-21 13:29 ` Tom Rini
2013-02-21 19:03 ` Stephen Warren
2013-02-21 10:37 ` Russell King - ARM Linux
2013-02-21 13:20 ` Tom Rini
2013-02-21 13:46 ` Russell King - ARM Linux
2013-02-21 14:08 ` Tom Rini
2013-02-21 14:37 ` Russell King - ARM Linux
2013-02-21 14:46 ` Tom Rini
2013-02-21 17:25 ` [U-Boot] " Nicolas Pitre
2013-02-21 17:40 ` Tom Rini
2013-02-21 19:21 ` Nicolas Pitre
2013-02-21 19:37 ` Stephen Warren
2013-02-21 19:57 ` Wolfgang Denk
2013-02-21 20:05 ` Stephen Warren
2013-02-21 20:18 ` Wolfgang Denk
2013-02-21 21:18 ` Nicolas Pitre
2013-02-22 0:10 ` Stephen Warren
2013-02-22 0:39 ` Russell King - ARM Linux
2013-02-22 20:48 ` Stephen Warren
2013-02-21 18:27 ` Jason Gunthorpe
2013-02-21 19:08 ` Russell King - ARM Linux
2013-02-21 20:15 ` Jason Gunthorpe
2013-02-21 19:57 ` Nicolas Pitre
2013-02-21 21:14 ` Jason Gunthorpe
2013-02-21 22:05 ` Nicolas Pitre
2013-02-21 23:11 ` Jason Gunthorpe
2013-02-21 23:50 ` Stephen Warren
2013-02-22 0:19 ` Scott Wood
2013-02-22 2:39 ` Jason Gunthorpe
2013-02-22 0:27 ` Russell King - ARM Linux
2013-02-22 0:41 ` Russell King - ARM Linux
2013-02-22 2:11 ` Jason Gunthorpe
2013-02-21 23:18 ` Wolfgang Denk
2013-02-21 23:28 ` Jason Gunthorpe
2013-02-22 0:19 ` Rob Herring
2013-02-22 2:22 ` Jason Gunthorpe
2013-02-22 3:32 ` Rob Herring
2013-02-22 7:56 ` Jason Kridner
2013-02-22 17:43 ` Jason Gunthorpe
2013-02-22 6:55 ` Wolfgang Denk
2013-02-21 23:45 ` Stephen Warren
2013-02-22 0:29 ` Russell King - ARM Linux
2013-02-21 20:56 ` Peter Korsgaard
2013-02-21 17:37 ` Wolfgang Denk
2013-02-21 18:33 ` Russell King - ARM Linux
2013-02-23 8:38 ` Joel A Fernandes
2013-02-22 16:00 ` Olof Johansson [this message]
2013-03-18 16:36 ` Pavel Machek
2013-03-18 16:44 ` Russell King - ARM Linux
2013-03-18 17:49 ` Pavel Machek
2013-03-18 17:57 ` Russell King - ARM Linux
2013-03-18 18:04 ` Pavel Machek
2013-03-18 18:14 ` [U-Boot] " Stephen Warren
2013-03-18 19:57 ` Wolfgang Denk
2013-03-18 19:51 ` Wolfgang Denk
2013-03-18 18:29 ` [U-Boot] " Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130222160044.GA16357@quad.lixom.net \
--to=olof@lixom.net \
--cc=agnel.joel@gmail.com \
--cc=glikely@secretlab.ca \
--cc=grant.likely@secretlab.ca \
--cc=joelagnel@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=trini@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox