ARM: Make ENTRY_FUNCTION more robust
An entry function should begin with a exception header. For this to work
properly the entry function should not contain any code which gcc might
put before the header. To make this sure change the ENTRY_FUNCTION macro
so that it generates one function which only contains the exception header
and a second function which contains the original body of the entry function.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
1 parent 509f622 commit 0644d1da7f547ba1b49ca95553ba65695ce9a3c3
@Sascha Hauer Sascha Hauer authored on 26 Nov 2013
Showing 16 changed files
View
arch/arm/boards/dfi-fs700-m60/lowlevel.c
View
arch/arm/boards/dmo-mx6-realq7/lowlevel.c
View
arch/arm/boards/ebv-socrates/lowlevel.c
View
arch/arm/boards/efika-mx-smartbook/lowlevel.c
View
arch/arm/boards/freescale-mx51-pdk/lowlevel.c
View
arch/arm/boards/freescale-mx53-loco/lowlevel.c
View
arch/arm/boards/freescale-mx53-vmx53/lowlevel.c
View
arch/arm/boards/freescale-mx6-sabrelite/lowlevel.c
View
arch/arm/boards/gk802/lowlevel.c
View
arch/arm/boards/phytec-pfla02/lowlevel.c
View
arch/arm/boards/solidrun-cubox/lowlevel.c
View
arch/arm/boards/terasic-sockit/lowlevel.c
View
arch/arm/boards/toradex-colibri-t20-iris/entry.c
View
arch/arm/boards/toshiba-ac100/entry.c
View
arch/arm/boards/tqma6x/lowlevel.c
View
arch/arm/include/asm/barebox-arm.h