Dear Lei Wen,
In message <1294654875-6414-1-git-send-email-lei...@marvell.com> you wrote:
> For uImage always has a 64 bytes header, we couldn't expect to do
> the xip from the header but should xip from the image start.
>
> The latter logic in that section is also move the image from image_start
On Saturday, February 05, 2011 02:57:42 Albert ARIBAUD wrote:
> Did you re-test patch V2?
i didnt test either ... v2 looks pretty straight forward though
Acked-by: Mike Frysinger
-mike
signature.asc
Description: This is a digitally signed message part.
_
On Thursday, February 03, 2011 21:32:10 Lei Wen wrote:
> On Mon, Jan 10, 2011 at 6:21 PM, Lei Wen wrote:
> > For uImage always has a 64 bytes header, we couldn't expect to do
> > the xip from the header but should xip from the image start.
> >
> > The latter logic in that section is also move the
Le 04/02/2011 03:32, Lei Wen a écrit :
> Hi Albert,
>
> On Mon, Jan 10, 2011 at 6:21 PM, Lei Wen wrote:
>> For uImage always has a 64 bytes header, we couldn't expect to do
>> the xip from the header but should xip from the image start.
>>
>> The latter logic in that section is also move the image
Hi Albert,
On Mon, Jan 10, 2011 at 6:21 PM, Lei Wen wrote:
> For uImage always has a 64 bytes header, we couldn't expect to do
> the xip from the header but should xip from the image start.
>
> The latter logic in that section is also move the image from image_start
> to the load address, so sync
For uImage always has a 64 bytes header, we couldn't expect to do
the xip from the header but should xip from the image start.
The latter logic in that section is also move the image from image_start
to the load address, so sync this logic to the xip operation.
Signed-off-by: Lei Wen
---
V2: kee
6 matches
Mail list logo
