Searched hist:aae2aef9c807a13ec9074efe48fae5bb5e3c6039 (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/arch/arm/include/asm/ |
| H A D | config.h | aae2aef9c807a13ec9074efe48fae5bb5e3c6039 Fri Jul 11 04:23:26 UTC 2014 Simon Glass <sjg@chromium.org> arm: Set up global data before board_init_f()
At present arm defines CONFIG_SYS_GENERIC_GLOBAL_DATA, meaning that
the global_data pointer is set up in board_init_f(). However it is
actually set up before this, it just isn't zeroed.
If we zero the global data before calling board_init_f() then we
don't need to define CONFIG_SYS_GENERIC_GLOBAL_DATA.
Make this change (on arm32 only) to simplify the init process. I
don't have the ability to test aarch64 yet.
Signed-off-by: Simon Glass <sjg@chromium.org>
Acked-by: Tom Rini <trini@ti.com>
|
| /rk3399_rockchip-uboot/arch/arm/lib/ |
| H A D | crt0.S | aae2aef9c807a13ec9074efe48fae5bb5e3c6039 Fri Jul 11 04:23:26 UTC 2014 Simon Glass <sjg@chromium.org> arm: Set up global data before board_init_f()
At present arm defines CONFIG_SYS_GENERIC_GLOBAL_DATA, meaning that
the global_data pointer is set up in board_init_f(). However it is
actually set up before this, it just isn't zeroed.
If we zero the global data before calling board_init_f() then we
don't need to define CONFIG_SYS_GENERIC_GLOBAL_DATA.
Make this change (on arm32 only) to simplify the init process. I
don't have the ability to test aarch64 yet.
Signed-off-by: Simon Glass <sjg@chromium.org>
Acked-by: Tom Rini <trini@ti.com>
|