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

[Jean-Christophe PLAGNIOL-VILLARD]

On 16:31 Mon 06 May     , Willy Tarreau wrote:
> Jean-Christophe,
> 
> On Mon, May 06, 2013 at 04:14:47PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > >  2) Because it's useful to extract the binary blob needed to configure
> > >  the DDR3 timing dynamically (for Armada 370/XP).
> > 
> > You do not read the comment
> > 
> > we need *runtime* update not *only* *xmodem* flashing. Barebox need to extract
> > by itself the information from a running platfrom in C
> > 
> > This is the barebox update that will ensure a binary is correct before
> > flashing and can only request barebox and not the blob stuff to udpate itself
> 
> I have read your comments as well and still don't understand what you want
> to explain. I think it would be more productive to spend the time to write
> real sentences and detailed explanations. Right now you're only in the
> "no thanks" mode and it's very hard to understand your concerns.
> 
> You can't blame people for not understanding you when you are the one who
> has difficulties explaining basic things in public.
so read the code of barebox before speaking

when I mention barebox update is a specific part of the code, if you do not
read the code you can not understand what I talk about. So no I'll not spend
time to explain you code that you did not read.
> 
> > > Have you read Sascha comment?
> > Yes you do not read what I write. I write *runtime* not *compiling* time
> 
> But for runtime to work, you need to boot at least once. The concern here
> is to get it to boot the first time, and for this, extracting the binary
> blob is needed.

No, it's not.
It's to simplify the job of hacker.
Not mandatory.

And it's does not require you to generate the image before flashing.
And request the blob by XMODEM will NEVER work to update at runtime as can not
discuss with the ROM code via XMODEM. So yes this will not work for self
update

Best Regards,
J.