[PATCH 2/7] scripts: new kwbimage manipulation tool for Marvell SoC boot images
Sascha Hauer
s.hauer at pengutronix.de
Mon May 6 16:56:31 EDT 2013
On Mon, May 06, 2013 at 10:44:56PM +0200, Thomas Petazzoni wrote:
> Dear Jean-Christophe PLAGNIOL-VILLARD,
>
> On Mon, 6 May 2013 22:35:40 +0200, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
>
> > this is where it's wrong, you does not need such binary at all, barebox update
> > will handle this by himself and will never requiere one image per media
> >
> > As barebox does not care wheren it boot from or where the dev is stored. we
> > choose is at runtime not at compile time
> >
> > Barebox update will generate the correct image for the storagemedia at
> > runtime
>
> What is "Barebox update" ?
barebox_update is a command that you can call during runtime to update
barebox. Over writing images directly to the storage it has the
advantage that you can do additional sanity checks on the images.
Also for example on i.MX a board specific poke table is all you need
to bring up SDRAM. As long as you have this poke table and a devicetree
you could use the same binary on different boards.
For initial bring up you would still need a SoC specific image though
(at least when not using JTAG), so you still need a tool to generate it.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox
mailing list