* Nicolas Pitre <nicolas.pitre@xxxxxxxxxx> [110421 16:18]: > On Thu, 21 Apr 2011, Tony Lindgren wrote: > > > Otherwise we end up overwriting ourselves. This fixes booting > > on n900 after commit 6d7d0ae51574943bf571d269da3243257a2d15db > > (ARM: 6750/1: improvements to compressed/head.S). > > > > Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx> > > I don't understand why this is needed. The copy loop is explicitly > copying from the end going backward exactly to cope with this > possibility. > > Hmmm... Yeah that's what I'm wondering too.. This is probably not the right fix.. I'm also wondering that it should be possible to make uImage also not work by setting loadaddr just before the uncompressed kernel end. You would assume that only the running code would not survive relocation if some of it gets overwritten. But that should be only the beginning, no idea why the need to relocate all the way after the whole image? If stack was overlapping the zImage, I could see it corrupt the zImage but there not much happening between relocating and restarting of the bootloader. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
