1. 24 8月, 2009 1 次提交
    • M
      start a linker script helper file · 6ac9f479
      Mike Frysinger 提交于
      Start a common header file for common linker script code (such as
      workarounds for older linkers) rather than doing this in the build system.
      
      As fallout, we no longer execute the linker every time config.mk is
      included by a build file (which can easily be 70+ times), but rather only
      execute it once.
      
      This also fixes a bug in the major version checking by creating a macro to
      easily compare versions and keep people from making the same common
      mistake (forgetting to check major and minor together).
      Signed-off-by: NMike Frysinger <vapier@gentoo.org>
      6ac9f479
  2. 23 8月, 2009 1 次提交
  3. 22 8月, 2009 2 次提交
    • P
      mpc83xx: sbc8349 - make enabling PCI more user friendly · c0d660fb
      Paul Gortmaker 提交于
      Prior to this commit, to enable PCI, you had to go manually
      edit the board config header, which isn't really user friendly.
      This adds the typical PCI make targets to the toplevel Makefile
      in accordance with what is being done with other boards.
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NKim Phillips <kim.phillips@freescale.com>
      c0d660fb
    • W
      Fix all linker scripts for older binutils versions (pre-2.16) · 1aada9cd
      Wolfgang Denk 提交于
      Commit f62fb999 fixed handling of all rodata sections by using a
      wildcard combined with calls to ld's builtin functions SORT_BY_ALIGNMENT()
      and SORT_BY_NAME().  Unfortunately these functions were only
      introduced with biunutils version 2.16, so the modification broke
      building with all tool chains using older binutils.
      
      This patch makes it work again.  This is done by omitting the use of
      these functions for such old tool chains.  This will result in
      slightly larger target binaries, as the rodata sections are no longer
      in optimal order alignment-wise which reauls in unused gaps, but the
      effect was found to be insignificant - especially compared to the fact
      that you cannot build U-Boot at all in the current state.
      
      As ld seems to have no support for conditionals we run the linker
      script through the C preprocessor which can be easily used to remove
      the unwanted function calls.
      
      Note that the C preprocessor must be run with the "-ansi" (or a
      "-std=") option to make sure all the system-specific predefined
      macros outside the reserved namespace are suppressed. Otherise, cpp
      might for example substitute "powerpc" to "1", thus corrupting for
      example "OUTPUT_ARCH(powerpc)" etc.
      Signed-off-by: NWolfgang Denk <wd@denx.de>
      Cc: Mike Frysinger <vapier@gentoo.org>
      1aada9cd
  4. 10 8月, 2009 1 次提交
  5. 28 7月, 2009 3 次提交
  6. 27 7月, 2009 2 次提交
    • W
      Prepare 2009.08-rc1 · 10c7604d
      Wolfgang Denk 提交于
      Update CHANGELOG, minor coding style fix.
      Signed-off-by: NWolfgang Denk <wd@denx.de>
      10c7604d
    • W
      Make linking against libgcc configurable · 52b1bf2c
      Wolfgang Denk 提交于
      Many (especially ARM) tool chains seem to come with broken or
      otherwise unusable (for the purposes of builing U-Boot) run-time
      support libraries `libgcc.a'. By using the "USE_PRIVATE_LIBGCC"
      setting we allow to use alternative libraries instead.
      
      "USE_PRIVATE_LIBGCC" can either be set as an environment variable in
      the shell, or as a command line argument when running "make", i. e.
      	$ make USE_PRIVATE_LIBGCC=yes
      or
      	$ USE_PRIVATE_LIBGCC=yes
      	$ export USE_PRIVATE_LIBGCC
      	$ make
      
      The value of "USE_PRIVATE_LIBGCC" is the name of the directory which
      contains the alternative run-time support library `libgcc.a'. The
      special value "yes" selects the directory $(OBJTREE)/lib_$(ARCH) .
      
      Note that not all architectures provide an alternative `libgcc.a' in
      their lib_$(ARCH) directories - so far, only ARM does.
      Signed-off-by: NWolfgang Denk <wd@denx.de>
      Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
      Cc: Prafulla Wadaskar <prafulla@marvell.com>
      cc: Stefan Roese <sr@denx.de>
      52b1bf2c
  7. 24 7月, 2009 5 次提交
  8. 23 7月, 2009 1 次提交
  9. 21 7月, 2009 2 次提交
  10. 20 7月, 2009 1 次提交
    • M
      push CROSS_COMPILE out to $(ARCH)_config.mk · 1ea6bcd8
      Mike Frysinger 提交于
      Each arch should handle setting a proper default CROSS_COMPILE value in
      their own config.mk file rather than having to maintain a large ugly list
      in the Makefile.  By using conditional assignment, we don't have to worry
      about the variable already being set (env/cmdline/etc...).
      
      The common config.mk file takes care of exporting CROSS_COMPILE already,
      and while a few variables (toolchain ones) utilize CROSS_COMPILE before
      including the arch config.mk, they do so with deferred assignment.
      Signed-off-by: NMike Frysinger <vapier@gentoo.org>
      1ea6bcd8
  11. 19 7月, 2009 4 次提交
  12. 18 7月, 2009 1 次提交
  13. 17 7月, 2009 1 次提交
    • S
      Remove legacy NAND and disk on chip code. · be33b046
      Scott Wood 提交于
      Legacy NAND had been scheduled for removal.  Any boards that use this
      were already not building in the previous release due to an #error.
      
      The disk on chip code in common/cmd_doc.c relies on legacy NAND,
      and it has also been removed.  There is newer disk on chip code
      in drivers/mtd/nand; someone with access to hardware and sufficient
      time and motivation can try to get that working, but for now disk
      on chip is not supported.
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      be33b046
  14. 14 7月, 2009 2 次提交
  15. 12 7月, 2009 2 次提交
  16. 11 7月, 2009 4 次提交
  17. 08 7月, 2009 2 次提交
  18. 07 7月, 2009 5 次提交