1. 04 6月, 2018 1 次提交
  2. 28 4月, 2018 1 次提交
    • A
      Convert CONFIG_SPI to Kconfig · f1b1f770
      Adam Ford 提交于
      This converts the following to Kconfig:
         CONFIG_SPI
      
      This partly involves updating code that assumes that CONFIG_SPI implies
      things that are specific to the MPC8xx SPI driver.  For now, just update
      the CONFIG tests.  This also involves reworking the default for
      CONFIG_SYS_DEF_EEPROM_ADDR so that we don't set it when we cannot make a
      reasonable default, as it does not cause any compile failures.
      Signed-off-by: NAdam Ford <aford173@gmail.com>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      f1b1f770
  3. 17 4月, 2018 1 次提交
  4. 07 4月, 2018 1 次提交
  5. 24 2月, 2018 1 次提交
  6. 11 2月, 2018 1 次提交
    • T
      configs: Migrate CONFIG_SYS_TEXT_BASE · 278b90ce
      Tom Rini 提交于
      On the NIOS2 and Xtensa architectures, we do not have
      CONFIG_SYS_TEXT_BASE set.  This is a strict migration of the current
      values into the defconfig and removing them from the headers.
      
      I did not attempt to add more default values in and for now will leave
      that to maintainers.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      278b90ce
  7. 06 2月, 2018 1 次提交
    • T
      cmd: Make CONFIG_CMD_FPGA depend on CONFIG_FPGA · a4fa8114
      Tuomas Tynkkynen 提交于
      cmd/Makefile has:
      
      ifdef CONFIG_FPGA
      obj-$(CONFIG_CMD_FPGA) += fpga.o
      endif
      
      which means that if CONFIG_FPGA is not set, CONFIG_CMD_FPGA silently
      does nothing. Let's remove that Makefile conditional and instead express
      this equivalent dependency in Kconfig, so a lot of redundant
      
       # CONFIG_CMD_FPGA is not set
      
      can be removed from board defconfigs that don't actually have an FPGA.
      Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>
      a4fa8114
  8. 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
  9. 28 8月, 2017 1 次提交
  10. 27 8月, 2017 1 次提交
  11. 15 8月, 2017 2 次提交
  12. 05 8月, 2017 1 次提交
  13. 01 8月, 2017 1 次提交
  14. 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
  15. 19 6月, 2017 1 次提交
  16. 10 5月, 2017 2 次提交
  17. 14 3月, 2017 1 次提交
  18. 30 12月, 2016 1 次提交
    • M
      mmc: complete unfinished move of CONFIG_MMC · c2726995
      Masahiro Yamada 提交于
      Commit 7a777f6d ("mmc: Add generic Kconfig option") created
      a Kconfig entry for this option without any actual moves, then
      commit 44c79879 ("sunxi: Use Kconfig CONFIG_MMC") moved
      instances only for SUNXI.
      
      We generally do not like such partial moves.  This kind of work
      is automated by tools/moveconfig.py, so it is pretty easy to
      complete this move.
      
      I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
      This shortens the configs and will ease new board porting.
      
      This commit was created as follows:
      
      [1] Edit Kconfig (remove the "depends on", add the "default",
          copy the prompt and help message from Linux)
      
      [2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
      c2726995
  19. 12 10月, 2016 1 次提交
  20. 10 9月, 2016 1 次提交
  21. 10 6月, 2016 1 次提交
  22. 26 4月, 2016 2 次提交
  23. 15 3月, 2016 1 次提交
  24. 28 9月, 2015 1 次提交
  25. 13 8月, 2015 1 次提交
    • N
      kconfig: add config option for shell prompt · 181bd9dc
      Nikita Kiryanov 提交于
      Add option to set shell prompt string from menuconfig and migrate
      boards globally.
      
      The migration is done as follows:
      - Boards that explicitly and unconditionally set CONFIG_SYS_PROMPT had the
        entry moved to their defconfig files.
      - Boards that defined some kind of #ifdef logic which selects the
        CONFIG_SYS_PROMPT (for example qemu-mips) got an #undef CONFIG_SYS_PROMPT
        right before the #ifdef logic and were left alone.
      - This change forces CONFIG_SYS_PROMPT to be a per board decision, and thus
        CONFIG_SYS_PROMPT was removed from all <soc>_common.h and <arch>_common.h
        files. This results in a streamlined default value across platforms, and
        includes the following files: spear-common, sunxi-common, mv-common,
        ti_armv7_common, tegra-common, at91-sama5_common, and zynq-common.
      - Boards that relied on <arch/soc>_common.h values of CONFIG_SYS_PROMPT were
        not updated in their respective defconfig files under the assumption that
        since they did not explicitly define a value, they're fine with whatever
        the default is.
      - On the other hand, boards that relied on a value defined in some
        <boards>_common.h file such as woodburn_common, rpi-common,
        bur_am335x_common, ls2085a_common, siemens_am33x_common, and
        omap3_evm_common, had their values moved to the respective defconfig files.
      - The define V_PROMPT was removed, since it is not used anywhere except for
        assigning a value for CONFIG_SYS_PROMPT.
      
      Cc: Tom Rini <trini@konsulko.com>
      Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Signed-off-by: NNikita Kiryanov <nikita@compulab.co.il>
      [trini: Add spring, sniper, smartweb to conversion]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      181bd9dc
  26. 26 6月, 2015 1 次提交
  27. 01 6月, 2015 1 次提交
  28. 13 5月, 2015 1 次提交
  29. 21 2月, 2015 1 次提交
  30. 30 7月, 2014 1 次提交
    • M
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada 提交于
      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: NMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: NSimon Glass <sjg@chromium.org>
      dd84058d