1. 13 Sep, 2014 1 commit
  2. 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.
      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>
    • 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>
  3. 12 Mar, 2014 1 commit
    • Masahiro Yamada's avatar
      kbuild: rename SRCTREE to srctree · 01286329
      Masahiro Yamada authored
      Prior to Kbuild, $(TOPDIR) or $(SRCTREE) was used for
      pointing to the top of source directory.
      (No difference between the two.)
      In Kbuild style, $(srctree) is used for instead.
      This commit renames SRCTREE to srctree and deletes the
      defition of SRCTREE.
      Note that SRCTREE in scripts/kernel-doc, scripts/docproc.c,
      doc/DocBook/Makefile should be keep.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
  4. 07 Mar, 2014 1 commit
  5. 01 Nov, 2013 1 commit
  6. 24 Jul, 2013 1 commit
  7. 29 Apr, 2011 1 commit
    • Scott Wood's avatar
      Handle most LDSCRIPT setting centrally · 83b7e2a7
      Scott Wood authored
      Currently, some linker scripts are found by common code in config.mk.
      Some are found using CONFIG_SYS_LDSCRIPT, but the code for that is
      sometimes in arch config.mk and sometimes in board config.mk.  Some
      are found using an arch-specific rule for looking in CPUDIR, etc.
      Further, the powerpc config.mk rule relied on CONFIG_NAND_SPL
      when it really wanted CONFIG_NAND_U_BOOT -- which covered up the fact
      that not all NAND_U_BOOT builds actually wanted CPUDIR/u-boot-nand.lds.
      Replace all of this -- except for a handful of boards that are actually
      selecting a linker script in a unique way -- with centralized ldscript
      If board code specifies LDSCRIPT, that will be used.
      Otherwise, if CONFIG_SYS_LDSCRIPT is specified, that will be used.
      If neither of these are specified, then the central config.mk will
      check for the existence of the following, in order:
      $(TOPDIR)/board/$(BOARDDIR)/u-boot-nand.lds (only if CONFIG_NAND_U_BOOT)
      $(TOPDIR)/$(CPUDIR)/u-boot-nand.lds (only if CONFIG_NAND_U_BOOT)
      Some boards (sc3, cm5200, munices) provided their own u-boot.lds that
      were dead code, because they were overridden by a CPUDIR u-boot.lds under
      the old powerpc rules.  These boards' own u-boot.lds have bitrotted and
      no longer work -- these lds files have been removed.
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      Tested-by: default avatarGraeme Russ <graeme.russ@gmail.com>
  8. 18 Oct, 2010 1 commit
  9. 12 Sep, 2008 1 commit
  10. 09 Sep, 2008 1 commit
  11. 05 Sep, 2008 1 commit
    • Ricardo Ribalda Delgado's avatar
      ppc44x: Unification of virtex5 pp440 boards · e07f4a80
      Ricardo Ribalda Delgado authored
      This patch provides an unificated way of handling xilinx v5 ppc440 boards.
      It unificates 3 different things:
      1) Source code
      A new board called ppc440-generic has been created. This board includes
      a generic tlb initialization (Maps the whole memory into virtual) and
      defines board_pre_init, checkboard, initdram and get_sys_info weakly,
      so, they can be replaced by specific functions.
      If a new board needs to redefine any of the previous functions
      (specific initialization) it can create a new directory with the
      specific initializations needed. (see the example ml507 board).
      2) Configuration file
      Common configurations are located under configs/xilinx-ppc440.h, this
      header file interpretes the xparameters file generated by EDK and
      configurates u-boot in correspondence. Example: if there is a Temac,
      allows CMD_CONFIG_NET
      Specific configuration are located under specific configuration file.
      (see the example ml507 board)
      3) Makefile
      Some work has been done in order to not duplicate work in the Main
      Makefile. Please see the attached code.
      In order to support new boards they can be implemented in the next way:
      a) Simple Generic Board  (90% of the time)
      Using EDK generates a new xparameters.h file, replace
      ppc440-generic/xparameters.h  and run make xilinx-ppc440-generic_config
      && make
      b) Simple Boards with special u-boot parameters (9 % of the time)
      Create a new file under configs for it (use ml507.h as example) and
      change your paramaters. Create a new Makefile paragraph and compile
      c) Complex boards (1% of the time)
      Create a new folder for the board, like the ml507
      Finally, it adds support for the Avnet FX30T Evaluation board, following
      the new generic structure:
      Cheap board by Avnet for evaluating the Virtex5 FX technology.
      This patch adds support for:
       - UartLite
       - 16MB Flash
       - 64MB RAM
      Prior using U-boot in this board, read carefully the ERRATA by Avnet
      to solve some memory initialization issues.
      Signed-off-by: default avatarRicardo Ribalda Delgado <ricardo.ribalda@uam.es>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
  12. 30 Jul, 2008 3 commits
  13. 18 Jul, 2008 1 commit
    • Ricardo Ribalda Delgado's avatar
      ppc4xx: ML507 Board Support · 086511fc
      Ricardo Ribalda Delgado authored
      The Xilinx ML507 Board is a Virtex 5 prototyping board that includes,
      	among others:
      	-Virtex 5 FX FPGA (With a ppc440x5 in it)
      	-256MB of SDRAM2
      	-32MB of Flash
      	-I2C Eeprom
      	-System ACE chip
      	-Serial ATA connectors
      	-RS232 Level Conversors
      	-Ethernet Transceiver
      This patch gives support to a standard design produced by EDK for this
      board: ppc440, uartlite, xilinx_int and flash
      - Includes Changes propossed by Stefan Roese and Michal Simek
      Signed-off-by: default avatarRicardo Ribalda Delgado <ricardo.ribalda@uam.es>
      Acked-by: default avatarStefan Roese <sr@denx.de>