On Fri, 21 Oct 2011 11:50:25 -0000, "Tixy \(Jon Medhurst\)" <879...@bugs.launchpad.net> wrote: > Public bug reported: > > The U-Boot bootcmd environment created by BoardConfig._get_bootcmd() > uses 'kernel_addr' for the address to load the uImage, it should use > 'load_addr' instead. The current use of 'kernel_addr ' has the effect of > loading the kernel to the address it will be run from, which U-Boot > interprets as meaning the image is XIP and will end up trying to boot > Linux by execute the image header and therefore crashing.
Is this something that should be applied to all boards? Why has no-one noticed this issue before? Thanks, James -- You received this bug notification because you are a member of linaro- infrastructure-drivers, which is the registrant for Linaro Image Tools. https://bugs.launchpad.net/bugs/879385 Title: boot.scr contains wrong kernel load address Status in Linaro Image Tools: New Bug description: The U-Boot bootcmd environment created by BoardConfig._get_bootcmd() uses 'kernel_addr' for the address to load the uImage, it should use 'load_addr' instead. The current use of 'kernel_addr ' has the effect of loading the kernel to the address it will be run from, which U-Boot interprets as meaning the image is XIP and will end up trying to boot Linux by execute the image header and therefore crashing. This affects booting Versatile Express with U-Boot. I have attached a patch which fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-image-tools/+bug/879385/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linaro-release Post to : linaro-release@lists.launchpad.net Unsubscribe : https://launchpad.net/~linaro-release More help : https://help.launchpad.net/ListHelp
