1. 15 6月, 2019 1 次提交
  2. 27 5月, 2019 1 次提交
  3. 18 5月, 2019 1 次提交
  4. 30 4月, 2019 1 次提交
  5. 26 3月, 2019 1 次提交
  6. 22 2月, 2019 1 次提交
  7. 14 2月, 2019 1 次提交
    • M
      ARM: zynq: Run distribution boot commands first · d13f92b7
      Michal Simek 提交于
      This patch is doing two things.
      1. Exchanging order of boot commands. distro_bootcmd is run first
      followed by Xilinx boot command.
      2. Remove CONFIG_BOOTCOMMAND from configs (and follow mainline) by
      creating Xilinx distribution bootcommand and wiring it as the last
      bootcommand.
      
      QSPI, NAND distribution boot command will be added later.
      Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
      d13f92b7
  8. 07 2月, 2019 1 次提交
  9. 24 1月, 2019 1 次提交
  10. 08 1月, 2019 1 次提交
  11. 04 9月, 2018 1 次提交
  12. 04 6月, 2018 1 次提交
  13. 11 5月, 2018 1 次提交
    • M
      arm: zynq: Remove checkboard and enable DISPLAY_CPUINFO · 0b4b82ad
      Michal Simek 提交于
      Now that showing silicon version is part of the CPU
      info display, let's remove checkboard().
      
      Note that the generic show_board_info() will still
      show the DT 'model' property. For instance:
      
      U-Boot 2018.05-rc2-00025-g611b3ee0159b (Apr 19 2018 - 11:23:12 +0200)
      
      CPU:   Zynq 7z045
      Silicon: v1.0
      Model: Zynq ZC706 Development Board
      I2C:   ready
      
      Based on patches from Ariel D'Alessandro <ariel@vanguardiasur.com.ar>,
      and Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
      
      mini configuration doesn't need to show this information.
      Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
      0b4b82ad
  14. 17 4月, 2018 1 次提交
  15. 12 4月, 2018 1 次提交
  16. 09 4月, 2018 1 次提交
  17. 23 3月, 2018 1 次提交
  18. 01 3月, 2018 3 次提交
  19. 28 2月, 2018 1 次提交
  20. 02 2月, 2018 1 次提交
  21. 30 1月, 2018 3 次提交
  22. 15 12月, 2017 1 次提交
  23. 28 11月, 2017 2 次提交
  24. 11 10月, 2017 1 次提交
    • T
      cmd: Toggle the default value of CONFIG_CMD_IMLS · ad12dc18
      Tuomas Tynkkynen 提交于
      Having this as a 'default y' is rather annoying because it doesn't
      actually compile unless other options are defined in the board header:
      
      ../cmd/bootm.c: In function 'do_imls_nor':
      ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
         i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {
      
      Make it 'default n' so people who develop new boards that start from a
      blank defconfig have one less compilation failure to debug.
      Signed-off-by: NTuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
      ad12dc18
  25. 04 10月, 2017 1 次提交
  26. 28 8月, 2017 1 次提交
  27. 15 8月, 2017 1 次提交
  28. 12 8月, 2017 1 次提交
  29. 26 7月, 2017 1 次提交
    • S
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass 提交于
      This converts the following to Kconfig:
         CONFIG_ENV_IS_IN_MMC
         CONFIG_ENV_IS_IN_NAND
         CONFIG_ENV_IS_IN_UBI
         CONFIG_ENV_IS_NOWHERE
      
      In fact this already exists for sunxi as a 'choice' config. However not
      all the choices are available in Kconfig yet so we cannot use that. It
      would lead to more than one option being set.
      
      In addition, one purpose of this series is to allow the environment to be
      stored in more than one place. So the existing choice is converted to a
      normal config allowing each option to be set independently.
      
      There are not many opportunities for Kconfig updates to reduce the size of
      this patch. This was tested with
      
         ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC
      
      And then manual updates.  This is because for CHAIN_OF_TRUST boards they
      can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
      now.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      2be29653
  30. 19 6月, 2017 1 次提交
  31. 13 2月, 2017 1 次提交
    • M
      flash: complete CONFIG_SYS_NO_FLASH move with renaming · e856bdcf
      Masahiro Yamada 提交于
      We repeated partial moves for CONFIG_SYS_NO_FLASH, but this is
      not completed. Finish this work by the tool.
      
      During this move, let's rename it to CONFIG_MTD_NOR_FLASH.
      Actually, we have more instances of "#ifndef CONFIG_SYS_NO_FLASH"
      than those of "#ifdef CONFIG_SYS_NO_FLASH".  Flipping the logic will
      make the code more readable.  Besides, negative meaning symbols do
      not fit in obj-$(CONFIG_...) style Makefiles.
      
      This commit was created as follows:
      
      [1] Edit "default n" to "default y" in the config entry in
          common/Kconfig.
      
      [2] Run "tools/moveconfig.py -y -r HEAD SYS_NO_FLASH"
      
      [3] Rename the instances in defconfigs by the following:
        find . -path './configs/*_defconfig' | xargs sed -i \
        -e '/CONFIG_SYS_NO_FLASH=y/d' \
        -e 's/# CONFIG_SYS_NO_FLASH is not set/CONFIG_MTD_NOR_FLASH=y/'
      
      [4] Change the conditionals by the following:
        find . -name '*.[ch]' | xargs sed -i \
        -e 's/ifndef CONFIG_SYS_NO_FLASH/ifdef CONFIG_MTD_NOR_FLASH/' \
        -e 's/ifdef CONFIG_SYS_NO_FLASH/ifndef CONFIG_MTD_NOR_FLASH/' \
        -e 's/!defined(CONFIG_SYS_NO_FLASH)/defined(CONFIG_MTD_NOR_FLASH)/' \
        -e 's/defined(CONFIG_SYS_NO_FLASH)/!defined(CONFIG_MTD_NOR_FLASH)/'
      
      [5] Modify the following manually
        - Rename the rest of instances
        - Remove the description from README
        - Create the new Kconfig entry in drivers/mtd/Kconfig
        - Remove the old Kconfig entry from common/Kconfig
        - Remove the garbage comments from include/configs/*.h
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      e856bdcf
  32. 10 2月, 2017 3 次提交
  33. 31 1月, 2017 1 次提交