Re: [PATCH 2/7] scripts: new kwbimage manipulation tool for Marvell SoC boot images

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Dear Sascha Hauer,

On Tue, 7 May 2013 11:47:52 +0200, Sascha Hauer wrote:

> > yes you need to construct the image at *runtime* and drop this madness of 1
> > image per media to generate. As this will create 1 defconfig per target device
> > 
> > which duplicate the defconfig and make the maintainance a nightmare
> 
> That's the way we currently do it. Don't expect from Thomas to do it
> differently as long there is not even a single example in the tree how
> to do it.

The Barebox image (barebox.bin) itself is *completely* independent from
the post-processing done by kwbimage. I.e, if I'm able to generate a
multiplatform barebox.bin that works on all Armada 370/XP boards, then
a single defconfig will be needed for all Armada 370/XP boards. This
defconfig will generate one single barebox.bin that works on all Armada
370/XP boards. Only the post-processing step to be done with kwbimage
will be board-specific, and this post-processing does not affect the
defconfig in any way. Of course, it remains to be defined how Barebox
will guess on which platform it runs (I suppose the idea is to somehow
bundle a DTB with Barebox, but I don't know).

Furthermore, the boot media is not selected in the Barebox
configuration, but only when running the kwbimage. So there is only one
barebox.bin per board, and one defconfig per board. Just like Barebox
is doing for all supported platforms at the moment.

So I'm not sure to see the connection between the number of defconfig
and the kwbimage tool. There is really no connection at all.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox