1. 25 May, 2015 1 commit
  2. 12 May, 2015 1 commit
  3. 29 Apr, 2015 1 commit
  4. 18 Apr, 2015 1 commit
  5. 08 Apr, 2015 1 commit
    • Masahiro Yamada's avatar
      ARM: zynq: disable CONFIG_SYS_MALLOC_F to fix MMC boot · 321f86e1
      Masahiro Yamada authored
      Since commit 326a6823 (malloc_f: enable SYS_MALLOC_F by default
      if DM is on), Zynq MMC boot hangs up after printing the following:
          U-Boot SPL 2015.04-rc5-00053-gadcc5705 (Apr 08 2015 - 12:59:11)
          mmc boot
          reading system.dtb
      Prior to commit 326a6823, Zynq boards enabled CONFIG_DM, but
      not CONFIG_SYS_MALLOC_F.  That commit forcibly turned on
      CONFIG_SYS_MALLOC_F.  I have not figured out the root cause, but
      anyway it looks like CONFIG_SYS_MALLOC_F gave a bad impact on the
      Zynq MMC boot.
      We are planning to have the v2015.04 release in a few days.
      I know this is a defensive fixup, but what I can do now is to add
         # CONFIG_SYS_MALLOC_F is not set
      to every Zynq defconfig file to get back the original behavior.
      Tested on:
        - Zedboard
        - ZC706 board
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Tested-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Cc: Simon Glass <sjg@chromium.org>
  6. 15 Mar, 2015 1 commit
  7. 30 Jan, 2015 2 commits
  8. 25 Sep, 2014 2 commits
  9. 31 Aug, 2014 1 commit
  10. 30 Jul, 2014 1 commit
    • 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>