On 05/10/2012 01:02 AM, Allen Martin wrote:
These flags were necessary when building tegra2 as a single binary that supported ARM7TDMI and Cortex A9. Now that the ARM7TDMI support is split into a separate SPL, this is no longer necessary.
diff --git a/arch/arm/cpu/armv7/tegra2/config.mk b/arch/arm/cpu/armv7/tegra2/config.mk
-# Tegra has an ARMv4T CPU which runs board_init_f(), so we must build this -# file with compatible flags -ifdef CONFIG_TEGRA2 -CFLAGS_arch/arm/lib/board.o += -march=armv4t -endif
That makes sense since the CFLAGS for the SPL build will be set up appropriately for the AVP.
-USE_PRIVATE_LIBGCC = yes
However, we force this because the toolchains we typically use for U-Boot are targeted at the A9 CPUs, and hence the libgcc there contains ARMv7 instructions. Did I miss something in this series or earlier that uses a different toolchain for the SPL, which includes an ARMv4 build of libgcc?