1. 09 7月, 2019 1 次提交
    • M
      at91, omap2plus: configs: migrate CONFIG_ENV_ to defconfigs · a9221f3e
      Markus Klotzbuecher 提交于
      Enable the extended ENV options for AT91 and OMAP2PLUS in order to be
      able to use CONFIG_ENV_UBI_* on these architectures.
      
      As this change also makes the configs ENV_SIZE, ENV_SECT_SIZE,
      ENV_OFFSET visible to AT91 and OMAP2PLUS, migrate users of these to
      KConfig.
      
      This migration was run using an extended moveconfig.py which evaluates
      expressions such as "(512 << 10)". See patch ("moveconfig: expand
      simple expressions").
      
      All modified boards were built with SOURCE_DATE_EPOCH=0 before and
      after the change and successfully confirmed that the identical binary
      is generated (the only exception was igep00x0, which does not define
      CONFIG_ENV_IS_IN_UBI in the original board header. Once that is
      defined, the test passes too).
      
      hs: rebased patch to:
        68b90e57: "configs: tinker-rk3288 disable CONFIG_SPL_I2C_SUPPORT"
      Signed-off-by: NMarkus Klotzbuecher <markus.klotzbuecher@kistler.com>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Eugen Hristev <eugen.hristev@microchip.com>
      Cc: Tom Rini <trini@konsulko.com>
      a9221f3e
  2. 30 4月, 2019 1 次提交
  3. 01 2月, 2019 1 次提交
  4. 14 11月, 2018 2 次提交
  5. 04 9月, 2018 1 次提交
  6. 18 8月, 2018 1 次提交
    • A
      Migrate bootlimit to Kconfig · ca0d535e
      Alex Kiernan 提交于
      Migrate boards which set bootlimit in the environment to Kconfig.
      
      We exclude gurnard_defconfig which includes a bootlimit=, but doesn't set
      CONFIG_BOOTCOUNT_LIMIT, so we'd fail to include a bootlimit setting
      if we migrated it.
      
      display5_defconfig and display5_factory_defconfig share a SYS_CONFIG_NAME,
      but only display5_defconfig enables CONFIG_BOOTCOUNT_LIMIT, so we fail to
      set bootlimit= in display5_factory_defconfig. This is okay because the
      display5_factory_defconfig doesn't need to have it set, as it is only
      meant to prepare the board in the factory.
      
      Environment changes for all modified configs as seen from buildman:
      
        boards.cfg is up to date. Nothing to do.
        Summary of 3 commits for 32 boards (8 threads, 1 job per thread)
        01: Merge git://git.denx.de/u-boot-x86
               arm:  +   draco etamin rastaban pxm2 display5 thuban rut
        02: Add BOOTCOUNT_BOOTLIMIT to set reboot limit
        03: Migrate bootlimit to Kconfig
           - display5_factory: bootlimit=3
      Signed-off-by: NAlex Kiernan <alex.kiernan@gmail.com>
      Reviewed-by: NLukasz Majewski <lukma@denx.de>
      ca0d535e
  7. 17 8月, 2018 1 次提交
    • T
      configs: Migrate CONFIG_NR_DRAM_BANKS · 86cf1c82
      Tom Rini 提交于
      We have the following cases:
      - CONFIG_NR_DRAM_BANKS was defined, migrate normally
      - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
        CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
      - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
        2), set this to 8.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      86cf1c82
  8. 04 6月, 2018 1 次提交
  9. 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
  10. 17 4月, 2018 1 次提交
  11. 12 4月, 2018 1 次提交
  12. 09 4月, 2018 1 次提交
  13. 08 4月, 2018 1 次提交
  14. 07 4月, 2018 1 次提交
  15. 24 2月, 2018 2 次提交
  16. 15 2月, 2018 1 次提交
  17. 23 1月, 2018 1 次提交
  18. 06 11月, 2017 1 次提交
  19. 31 10月, 2017 1 次提交
  20. 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
  21. 04 10月, 2017 2 次提交
  22. 28 8月, 2017 1 次提交
  23. 15 8月, 2017 1 次提交
  24. 14 8月, 2017 1 次提交
  25. 12 8月, 2017 1 次提交
  26. 08 8月, 2017 1 次提交
  27. 05 8月, 2017 1 次提交
  28. 01 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. 10 6月, 2017 1 次提交
  32. 15 5月, 2017 1 次提交
    • T
      watchdog: Migrate OMAP_WATCHDOG to Kconfig · 897f7062
      Tom Rini 提交于
      Move this entry to Kconfig.  As it is a hardware watchdog, select
      HW_WATCHDOG.  While we could default to enabling this for all platforms,
      it is currently only enabled by default on AM33XX, so keep that logic
      today.
      
      Cc: Roger Meier <r.meier@siemens.com>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      897f7062
  33. 12 5月, 2017 1 次提交
  34. 28 4月, 2017 1 次提交
  35. 14 3月, 2017 1 次提交
  36. 28 1月, 2017 1 次提交
  37. 26 1月, 2017 1 次提交