Skip to content
Snippets Groups Projects
  1. Nov 13, 2009
  2. Oct 27, 2009
  3. Oct 05, 2009
  4. Sep 15, 2009
  5. Sep 04, 2009
    • Mike Frysinger's avatar
      push LOAD_ADDR out to arch mk files · 262ae0a6
      Mike Frysinger authored
      
      Rather than maintain/extend the current ifeq($(ARCH)) mess that exists in
      the standalone Makefile, push the setting up of LOAD_ADDR out to the arch
      config.mk (and rename to STANDALONE_LOAD_ADDR in the process).  This keeps
      the common code clean and lets the arch do whatever crazy crap it wants in
      its own area.
      
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      262ae0a6
    • Mike Frysinger's avatar
      atmel_df_pow2: standalone to convert dataflashes to pow2 · 65f6f07b
      Mike Frysinger authored
      
      Atmel DataFlashes by default operate with pages that are slightly bigger
      than normal binary sizes (i.e. many are 1056 byte pages rather than 1024
      bytes).  However, they also have a "power of 2" mode where the pages show
      up with the normal binary size.  The latter mode is required in order to
      boot with a Blackfin processor, so many people wish to convert their
      DataFlashes on their development systems to this mode.  This standalone
      application does just that.
      
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      65f6f07b
  6. Sep 02, 2009
  7. Aug 08, 2009
    • 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
  8. Jul 27, 2009
  9. Jul 21, 2009
  10. Jul 20, 2009
  11. Apr 04, 2009
  12. Mar 20, 2009
    • 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
  13. Mar 18, 2009
  14. Feb 23, 2009
  15. Jan 24, 2009
  16. Dec 09, 2008
  17. Nov 18, 2008
  18. Oct 18, 2008
  19. Oct 14, 2008
  20. Sep 09, 2008
  21. Aug 31, 2008
  22. Jul 10, 2008
  23. May 20, 2008
    • 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
  24. May 18, 2008
  25. Apr 08, 2008
  26. Mar 04, 2008
  27. Mar 02, 2008
    • 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
  28. Feb 17, 2008
  29. Feb 14, 2008
    • 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
  30. Feb 07, 2008
  31. Feb 05, 2008
  32. Jan 12, 2008
    • 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
  33. Dec 27, 2007
  34. Nov 25, 2007
  35. Nov 15, 2007
Loading