summaryrefslogtreecommitdiff
path: root/drivers/video/mxsfb.c
diff options
context:
space:
mode:
authorAlbert ARIBAUD <albert.u.boot@aribaud.net>2015-11-25 17:56:33 +0100
committerTom Rini <trini@konsulko.com>2016-01-13 21:05:18 -0500
commitadc421e4cee8275cd99367b3b455ffbb5ead3990 (patch)
tree08a51a4c9a9a6d5806d9f2c329065de3a5a7586e /drivers/video/mxsfb.c
parentecc306639e83c9019a5093b77a48685ea40eedc2 (diff)
downloadu-boot-imx-adc421e4cee8275cd99367b3b455ffbb5ead3990.zip
u-boot-imx-adc421e4cee8275cd99367b3b455ffbb5ead3990.tar.gz
u-boot-imx-adc421e4cee8275cd99367b3b455ffbb5ead3990.tar.bz2
arm: move gd handling outside of C code
As of gcc 5.2.1 for Thumb-1, it is not possible any more to assign gd from C code, as gd is mapped to r9, and r9 may now be saved in the prolog sequence, and restored in the epilog sequence, of any C functions. Therefore arch_setup_gd(), which is supposed to set r9, may actually have no effect, causing U-Boot to use a bad address to access GD. Fix this by never calling arch_setup_gd() for ARM, and instead setting r9 in arch/arm/lib/crt0.S, to the value returned by board_init_f_alloc_reserve(). Signed-off-by: Albert ARIBAUD <albert.u.boot@aribaud.net> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/video/mxsfb.c')
0 files changed, 0 insertions, 0 deletions