1. 30 Jul, 2014 2 commits
    • Masahiro Yamada's avatar
      Add board MAINTAINERS files · 93d4334f
      Masahiro Yamada authored
      
      
      We have switched to Kconfig and the boards.cfg file is going to
      be removed. We have to retrieve the board status and maintainers
      information from it.
      
      The MAINTAINERS format as in Linux Kernel would be nice
      because we can crib the scripts/get_maintainer.pl script.
      
      After some discussion, we chose to put a MAINTAINERS file under each
      board directory, not the top-level one because we want to collect
      relevant information for a board into a single place.
      
      TODO:
      Modify get_maintainer.pl to scan multiple MAINTAINERS files.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Suggested-by: default avatarTom Rini <trini@ti.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      93d4334f
    • Masahiro Yamada's avatar
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada authored
      
      
      This commit adds:
       - arch/${ARCH}/Kconfig
          provide a menu to select target boards
       - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
          set CONFIG macros to the appropriate values for each board
       - configs/${TARGET_BOARD}_defconfig
          default setting of each board
      
      (This commit was automatically generated by a conversion script
      based on boards.cfg)
      
      In Linux Kernel, defconfig files are located under
      arch/${ARCH}/configs/ directory.
      It works in Linux Kernel since ARCH is always given from the
      command line for cross compile.
      
      But in U-Boot, ARCH is not given from the command line.
      Which means we cannot know ARCH until the board configuration is done.
      That is why all the "*_defconfig" files should be gathered into a
      single directory ./configs/.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      dd84058d
  2. 01 Nov, 2013 1 commit
  3. 24 Jul, 2013 1 commit
  4. 10 May, 2013 1 commit
  5. 08 Jan, 2013 1 commit
  6. 07 Jul, 2012 1 commit
  7. 27 Oct, 2011 1 commit
  8. 15 Oct, 2011 1 commit
  9. 17 Nov, 2010 1 commit
    • Sebastien Carlier's avatar
      Switch from archive libraries to partial linking · 6d8962e8
      Sebastien Carlier authored
      
      
      Before this commit, weak symbols were not overridden by non-weak symbols
      found in archive libraries when linking with recent versions of
      binutils.  As stated in the System V ABI, "the link editor does not
      extract archive members to resolve undefined weak symbols".
      
      This commit changes all Makefiles to use partial linking (ld -r) instead
      of creating library archives, which forces all symbols to participate in
      linking, allowing non-weak symbols to override weak symbols as intended.
      This approach is also used by Linux, from which the gmake function
      cmd_link_o_target (defined in config.mk and used in all Makefiles) is
      inspired.
      
      The name of each former library archive is preserved except for
      extensions which change from ".a" to ".o".  This commit updates
      references accordingly where needed, in particular in some linker
      scripts.
      
      This commit reveals board configurations that exclude some features but
      include source files that depend these disabled features in the build,
      resulting in undefined symbols.  Known such cases include:
      - disabling CMD_NET but not CMD_NFS;
      - enabling CONFIG_OF_LIBFDT but not CONFIG_QE.
      Signed-off-by: default avatarSebastien Carlier <sebastien.carlier@gmail.com>
      6d8962e8
  10. 28 Oct, 2010 1 commit
    • Prafulla Wadaskar's avatar
      kirkwood: get rid of config.mk files · 31d80c77
      Prafulla Wadaskar authored
      
      
      After moving the definition of CONFIG_SYS_TEXT_BASE to the respective
      board config files, all Marvell kirkwood board have just a single and
      common entry in their config.mk files:
      
      	KWD_CONFIG = $(SRCTREE)/board/$(BOARDDIR)/kwbimage.cfg
      
      Replace the only reference to KWD_CONFIG in the top level Makefile by
      an equivalent setting, and remove all kirkwood config.mk files.
      
      Signed-off-by: Wolfgang Denk <wd at denx.de>
      Cc: Prafulla Wadaskar <prafulla at marvell.com>
      Cc: Siddarth Gore <gores at marvell.com>
      Cc: Simon Kagstrom <simon.kagstrom at netinsight.net>
      Cc: Heiko Schocher <hs at denx.de>
      Cc: Eric Cooper <ecc at cmu.edu>
      Acked-by: Wolfgang Denk <wd at denx.de>
      Signed-off-by: default avatarPrafulla Wadaskar <prafulla@marvell.com>
      31d80c77
  11. 20 Oct, 2010 1 commit
  12. 18 Oct, 2010 1 commit
    • Wolfgang Denk's avatar
      Rename TEXT_BASE into CONFIG_SYS_TEXT_BASE · 14d0a02a
      Wolfgang Denk authored
      
      
      The change is currently needed to be able to remove the board
      configuration scripting from the top level Makefile and replace it by
      a simple, table driven script.
      
      Moving this configuration setting into the "CONFIG_*" name space is
      also desirable because it is needed if we ever should move forward to
      a Kconfig driven configuration system.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      14d0a02a
  13. 13 Oct, 2010 1 commit
    • Prafulla Wadaskar's avatar
      Kirkwood: dram_init is moved to dram.c · beeb2589
      Prafulla Wadaskar authored
      
      
      For all Kirkwood boards so far dram_init function is duplicated
      dram_init function is moved to dram.c and relevant code from all
      board specific files removed
      
      If any board needs specific dram init handling than standard one,
      then, a macro CONFIG_SYS_BOARD_DRAM_INIT should be defined in
      board config header file and the dram_init function can be put
      in board specific source file
      For ex. keymile boards
      Signed-off-by: default avatarPrafulla Wadaskar <prafulla@marvell.com>
      beeb2589
  14. 12 Oct, 2010 1 commit
    • Prafulla Wadaskar's avatar
      Kirkwood: dram_init is moved to dram.c · 6edf0f12
      Prafulla Wadaskar authored
      
      
      For all Kirkwood boards so far dram_init function is duplicated
      dram_init function is moved to dram.c and relevant code from all
      board specific files removed
      
      If any board needs specific dram init handling than standard one,
      then, a macro CONFIG_SYS_BOARD_DRAM_INIT should be defined in
      board config header file and the dram_init function can be put
      in board specific source file
      For ex. keymile boards
      Signed-off-by: default avatarPrafulla Wadaskar <prafulla@marvell.com>
      6edf0f12
  15. 13 Oct, 2009 1 commit
  16. 03 Oct, 2009 1 commit
  17. 18 Jul, 2009 1 commit