---------- Forwarded message ---------- From: Kiril Maler <[email protected]> Date: 14 January 2013 09:46 Subject: Workaround for hanging u-boot 'Load Address: fffffff2' To: "[email protected]" <[email protected]>
If your fresh uImage hangs in a similar way: ## Booting kernel from Legacy Image at 81000000 ... Image Name: Linux-3.8.0-rc2-tst04+ Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1161118 Bytes = 1.1 MiB Load Address: fffffff2 Entry Point: fffffff2 Verifying Checksum ... OK Loading Kernel Image ... Then a temporary fix could be added in arch/arm/boot/Makefile git diff arch/arm/boot/Makefile diff --git a/arch/arm/boot/Makefile b/arch/arm/boot/Makefile index abfce28..4182943 100644 --- a/arch/arm/boot/Makefile +++ b/arch/arm/boot/Makefile @@ -13,6 +13,8 @@ ifneq ($(MACHINE),) include $(srctree)/$(MACHINE)/Makefile.boot +else +include $(srctree)/arch/arm/mach-omap2/Makefile.boot endif # Note: the following conditions must always be true: Change 'mach-omap2' in the patch above to required machine directory This is needed because 'MACHINE' in arch/arm/Makefile is set empty when CONFIG_ARCH_MULTIPLATFORM=y, and consequently parameters -a and -e are empty in arch/arm/boot/.uImage.cmd Regards, -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
