mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-26 04:53:42 +00:00
64134f0112
With recent toolchain versions, some boards would not build because or errors like this one (here for ocotea board when building with ELDK 4.2 beta): ppc_4xx-ld: section .bootpg [fffff000 -> fffff23b] overlaps section .bss [fffee900 -> fffff8ab] For many boards, the .bss section is big enough that it wraps around at the end of the address space (0xFFFFFFFF), so the problem will not be visible unless you use a 64 bit tool chain for development. On some boards however, changes to the code size (due to different optimizations) we bail out with section overlaps like above. The fix is to add the NOLOAD attribute to the .bss and .sbss sections, telling the linker that .bss does not consume any space in the image. Signed-off-by: Wolfgang Denk <wd@denx.de> |
||
|---|---|---|
| .. | ||
| config.mk | ||
| ee_access.c | ||
| ee_access.h | ||
| ee_dev.h | ||
| flash.c | ||
| gth.c | ||
| Makefile | ||
| pcmcia.c | ||
| README | ||
| u-boot.lds | ||
Written by Thomas.Lange@corelatus.com 010805 To make a system for gth that actually works ;-) the variable TBASE needs to be set to 0,1 or 2 depending on location where image is supposed to be started from. E.g. make TBASE=1 0: Start from RAM, base 0 1: Start from flash_base + 0x10070 2: Start from flash_base + 0x30070 When using 1 or 2, the image is supposed to be launched from miniboot that boots the first U-Boot image found in flash. For miniboot code, description, see www.opensource.se