1. 08 Aug, 2009 1 commit
    • Michael Evans's avatar
      Fix examples for OMAP3 boards... · 61c68ae0
      Michael Evans authored
      The attached patch corrects an error in the examples/Makefile which
      causes the applications in the examples directory to hang on OMAP3
      based boards. The current Makefile sets -Ttext during linking to
      0x0c100000 which is outside of addressable SDRAM memory. The script
      corrects the existing ifeq...else...endif logic to look at the VENDOR
      tag rather than the CPU tag.
      
      The patch affects the following configs: omap3_beagle_config,
      omap3_overo_config, omap3_evm_config, omap3_pandora_config,
      omap3_zoom1_config and omap3_zoom2_config.
      Signed-off-by: default avatarMichael Evans <horse_dung@hotmail.com>
      
      Edited commit message.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      61c68ae0
  2. 27 Jul, 2009 1 commit
  3. 21 Jul, 2009 1 commit
  4. 20 Jul, 2009 1 commit
  5. 04 Apr, 2009 1 commit
  6. 20 Mar, 2009 1 commit
    • Trent Piepho's avatar
      Fix all linker script to handle all rodata sections · f62fb999
      Trent Piepho authored
      A recent gcc added a new unaligned rodata section called '.rodata.str1.1',
      which needs to be added the the linker script.  Instead of just adding this
      one section, we use a wildcard ".rodata*" to get all rodata linker section
      gcc has now and might add in the future.
      
      However, '*(.rodata*)' by itself will result in sub-optimal section
      ordering.  The sections will be sorted by object file, which causes extra
      padding between the unaligned rodata.str.1.1 of one object file and the
      aligned rodata of the next object file.  This is easy to fix by using the
      SORT_BY_ALIGNMENT command.
      
      This patch has not be tested one most of the boards modified.  Some boards
      have a linker script that looks something like this:
      
      *(.text)
      . = ALIGN(16);
      *(.rodata)
      *(.rodata.str1.4)
      *(.eh_frame)
      
      I change this to:
      
      *(.text)
      . = ALIGN(16);
      *(.eh_frame)
      *(SORT_BY_ALIGNMENT(SORT_BY_NAME(.rodata*)))
      
      This means the start of rodata will no longer be 16 bytes aligned.
      However, the boundary between text and rodata/eh_frame is still aligned to
      16 bytes, which is what I think the real purpose of the ALIGN call is.
      Signed-off-by: default avatarTrent Piepho <xyzzy@speakeasy.org>
      f62fb999
  7. 18 Mar, 2009 1 commit
  8. 23 Feb, 2009 1 commit
  9. 24 Jan, 2009 1 commit
  10. 09 Dec, 2008 1 commit
  11. 18 Nov, 2008 1 commit
  12. 18 Oct, 2008 1 commit
  13. 14 Oct, 2008 1 commit
  14. 09 Sep, 2008 1 commit
  15. 31 Aug, 2008 1 commit
  16. 10 Jul, 2008 2 commits
  17. 20 May, 2008 1 commit
    • Wolfgang Denk's avatar
      Big white-space cleanup. · 53677ef1
      Wolfgang Denk authored
      This commit gets rid of a huge amount of silly white-space issues.
      Especially, all sequences of SPACEs followed by TAB characters get
      removed (unless they appear in print statements).
      
      Also remove all embedded "vim:" and "vi:" statements which hide
      indentation problems.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      53677ef1
  18. 18 May, 2008 1 commit
  19. 08 Apr, 2008 1 commit
  20. 04 Mar, 2008 1 commit
  21. 02 Mar, 2008 1 commit
    • Woodruff, Richard's avatar
      Fix alignment error on ARM for modules · 118978c8
      Woodruff, Richard authored
      Fix alignment fault on ARM when running modules.  With out an explicit
      linker file gcc4.2.1 will half word align __bss_start's value.  The word
      dereference will crash hello_world.
      
      signed-off-by Richard Woodruff <r-woodruff2@ti.com>
      118978c8
  22. 17 Feb, 2008 1 commit
  23. 14 Feb, 2008 1 commit
    • Wolfgang Denk's avatar
      PPC: Use r2 instead of r29 as global data pointer · e7670f6c
      Wolfgang Denk authored
      R29 was an unlucky choice as with recent toolchains (gcc-4.2.x) gcc
      will refuse to use load/store multiple insns; instead, it issues a
      list of simple load/store instructions upon function entry and exit,
      resulting in bigger code size, which in turn makes the build for a
      few boards fail.
      
      Use r2 instead.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      e7670f6c
  24. 07 Feb, 2008 1 commit
  25. 05 Feb, 2008 4 commits
  26. 12 Jan, 2008 1 commit
    • Wolfgang Denk's avatar
      Fix linker scripts: add NOLOAD atribute to .bss/.sbss sections · 64134f01
      Wolfgang Denk authored
      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: default avatarWolfgang Denk <wd@denx.de>
      64134f01
  27. 27 Dec, 2007 1 commit
  28. 25 Nov, 2007 1 commit
  29. 15 Nov, 2007 1 commit
  30. 21 Oct, 2007 3 commits
  31. 13 May, 2007 1 commit
  32. 18 Mar, 2007 1 commit
  33. 09 Mar, 2007 1 commit
  34. 24 Oct, 2006 1 commit