On Fri, Oct 21, 2011 at 1:50 PM, Tixy (Jon Medhurst) <[email protected]> wrote: > ** Patch added: "Fix for BoardConfig._get_bootcmd()" > > https://bugs.launchpad.net/bugs/879385/+attachment/2564282/+files/boards.py.patch
I'm afraid that the patch may cause problems with all the other boards, since it uses the load_addr for something that current hwpacks do not expect. I'm not certain that the other boards will have problems, but to be confident we should test this very carefully. -- 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 : [email protected] Unsubscribe : https://launchpad.net/~linaro-release More help : https://help.launchpad.net/ListHelp
