UBoot

Hi cybdenw,

> It does seem to be down to the cache not flushing before jumping

> to the newly relocated code.

Ok ... then this is a bug in u-boot that needs fixing. The code in

the common tree _should_ take care of flushing the data cache

AND invalidating the instruction cache for the bootm target address

range (as it does for commands like loadb) ... but I sure can't find it

anywhere 8-/

I'll contact the main u-boot maintainers for some guidance on how to

proceed ... a board port shouldn't have to worry about this ... it should

be handled in the architecture-specific code.

Thanks for tracking this down :-)

Regards,

--Scott