* Nicolas Pitre <nicolas.pitre@xxxxxxxxxx> [110419 06:24]: > On Tue, 19 Apr 2011, Tony Lindgren wrote: > > > Aaro and I speculated that boards using u-boot with uImage work, > > while n900 is using zImage and fails with the same kernel probably > > because of the different placement of compressed image in the > > memory. > > Could you try the following (by changing the argument to mkimage > accordingly). > > Try to load the kernel at the following offsets: > > - 0x8000 from start of memory > > - 0x100000 from start of memory > > - 0x3000000 from start of memory > > and tell me if any of those behaves differently? Hmm good idea, but no luck so far :( Did the tests with setenv loadaddr in u-boot as that's what it seems to use. v2.6.39-rc4 boots uImage with all those just fine. And with the DT append and related patches, it always fails if DT data is appended. So for some reason loading a kernel on n900 with flasher -l always fails (except for smaller kernels) and DT append with data appended always fails. Regards, 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
