ARM: OMAP: Safe boot info in fixed SRAM address
Storing the boot information in the image itself and passing a pointer
around between images is cumbersome and doesn't fit well with multiimage
support where the pointer we pass around is already occupied by the
devicetree.
Do the same as U-Boot does and store the boot information at the bottom
of the SRAM public stack.
To maintain the compatibility between new xloaders and older barebox
binaries we still pass the boot information to the next stage via pointer.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
1 parent b037240 commit ee7f5d5d506e40b9707611eba6e40d76f8049b3b
@Sascha Hauer Sascha Hauer authored on 26 Nov 2013
Showing 13 changed files
View
arch/arm/mach-omap/Makefile
View
arch/arm/mach-omap/am33xx_generic.c
View
arch/arm/mach-omap/include/mach/am33xx-generic.h
View
arch/arm/mach-omap/include/mach/am33xx-silicon.h
View
arch/arm/mach-omap/include/mach/generic.h
View
arch/arm/mach-omap/include/mach/omap3-generic.h
View
arch/arm/mach-omap/include/mach/omap3-silicon.h
View
arch/arm/mach-omap/include/mach/omap4-generic.h
View
arch/arm/mach-omap/include/mach/omap4-silicon.h
View
arch/arm/mach-omap/omap3_generic.c
View
arch/arm/mach-omap/omap4_generic.c
View
arch/arm/mach-omap/omap_bootinfo.S 100644 → 0
View
arch/arm/mach-omap/omap_generic.c