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

[Jean-Christophe PLAGNIOL-VILLARD]

On 10:21 Mon 06 May     , Jason Cooper wrote:
> On Mon, May 06, 2013 at 04:04:39PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 16:06 Mon 06 May     , Thomas Petazzoni wrote:
> > > Dear Jean-Christophe PLAGNIOL-VILLARD,
> > > 
> > > On Mon, 6 May 2013 15:54:35 +0200, Jean-Christophe PLAGNIOL-VILLARD
> > > wrote:
> > > 
> > > > > Could you please adopt a nicer language? You are very aggressive... and
> > > > > at that the same time completely wrong. Your comments make it entirely
> > > > > clear that you haven't even read the comments at the top of file.
> > > > I did but still think we can handle it in C
> > > > 
> > > > and need to handle by barebox itself when flashing
> > > 
> > > The image is pushed to the target through X-modem, directly talking to
> > > the ROM code of the SoC. Do you want the kwboot tool to prepare the
> > > image? It seems to me like it makes a lot more sense to have a tool to
> > > prepare the image.
> > 
> > yes a you want to re-flash barebox itself and you will do for ddr and I do not
> > want to care about all of this blob stuff twht the board already known
> > 
> > > 
> > > Remember also that this tool is needed to *extract* existing images.
> > > And you haven't explained how you intend to do this without a proper
> > > userspace tool such as kwbimage.
> > 
> > why extract?
> 
> Because you *received* the blob over xmodem from the SoC.  It came from
> the factory that way.  You need to take it apart to get the DDR info and
> the stock bootloader blob.  Think of this as a tool to assist board
> hackers when the mfgr doesn't have the time/experience to help the open
> source community.
This will only work if you known the DDR which is a huge suposition.

When porting barebox on new hardware this will not help at all

so not this tool can not be the default tool generate fashable images
> 
> Since a separate tool is needed to do this, it makes sense to have the
> same code perform the packing as well.  As opposed to the CPP.
> 
> hth,
> 
> Jason.