On Tue, Jan 19, 2010 at 23:28, Song, Barry wrote:
>From: Mike Frysinger [mailto:[email protected]]
>>On Tue, Jan 19, 2010 at 22:22, Song, Barry wrote:
>>>From: Mike Frysinger [mailto:[email protected]]
>>>>## Booting kernel from Legacy Image at 20040000 ...
>>>> Image Name: bf537-2.6.32.4-ADI-2010R1-pre-gc
>>>> Created: 2010-01-19 23:54:17 UTC
>>>> Image Type: Blackfin Linux Kernel Image (uncompressed)
>>>> Data Size: 2902096 Bytes = 2.8 MB
>>>> Load Address: 20040040
>>>> Entry Point: 200f8534
>>>> Verifying Checksum ... OK
>>>> Loading Kernel Image ... OK
>>>>OK
>>>>Starting Kernel at = 200f8534
>>
>>i went through the u-boot code some more as this output didnt look
>>exactly right to me ... turns out there is some assumptions in the
>>bootm code. if the entry point isnt at the bootm address + 64bytes,
>>it'll assume a non-xip kernel. so when it says "loading", it actually
>>means it's doing a memcpy. it should have said "XIP ...". i'll poke
>>around u-boot to try and get this fixed.
>
> Sounds good. So XIP should be just a flag in image header, not need offset
> check :-)
nm, we dont need to change u-boot. the "loading" rather than "xip" is
OK as it is just a display. the code does:
if (load != image_start) {
memmove_wd ((void *)load,
(void *)image_start, image_len, CHUNKSZ);
and since load == image_start == 20040040, there is no memcpy
-mike
_______________________________________________
Linux-kernel-commits mailing list
[email protected]
https://blackfin.uclinux.org/mailman/listinfo/linux-kernel-commits
