1. 22 7月, 2018 2 次提交
  2. 19 7月, 2018 1 次提交
  3. 13 6月, 2018 2 次提交
  4. 09 4月, 2018 1 次提交
  5. 07 4月, 2018 1 次提交
    • R
      Allow providing default environment from file · f3d8f7dd
      Rasmus Villemoes 提交于
      Modifying the default environment via CONFIG_EXTRA_ENV_SETTINGS is
      somewhat inflexible, partly because the cpp language does not allow
      appending to an existing macro. This prevents reuse of "environment
      fragments" for different boards, which in turn makes maintaining that
      environment consistently tedious and error-prone.
      
      This implements a Kconfig option for allowing one to define the entire
      default environment in an external file, which can then, for example, be
      generated programmatically as part of a Yocto recipe, or simply be kept
      in version control separately from the U-boot repository.
      Tested-by: NSean Nyekjaer <sean.nyekjaer@prevas.dk>
      Signed-off-by: NRasmus Villemoes <rasmus.villemoes@prevas.dk>
      Reviewed-by: NLukasz Majewski <lukma@denx.de>
      f3d8f7dd
  6. 04 4月, 2018 1 次提交
  7. 24 3月, 2018 2 次提交
    • P
      Convert CONFIG_UBI_SILENCE_MSG to Kconfig · c0ce4cea
      Petr Vorel 提交于
      Signed-off-by: NPetr Vorel <petr.vorel@gmail.com>
      c0ce4cea
    • P
      Convert CONFIG_UBIFS_SILENCE_MSG to Kconfig · afb6fda2
      Petr Vorel 提交于
      Introduce another difference from upstream (kernel) source in
      fs/ubifs/super.c: adding preprocessor condition as y variable in
      mount_ubifs() depends on CONFIG_UBIFS_SILENCE_MSG:
      fs/ubifs/super.c:1337:15: error: variable ?y? set but not used [-Werror=unused-but-set-variable]
        long long x, y;
      
      Not setting CONFIG_UBIFS_SILENCE_MSG in am335x_igep003x_defconfig and
      igep0032_defconfig. Although it was defined in their config headers, it
      depends on CMD_UBIFS which is not set for them.
      Signed-off-by: NPetr Vorel <petr.vorel@gmail.com>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      Cc: Heiko Schocher <hs@denx.de>
      afb6fda2
  8. 27 1月, 2018 3 次提交
  9. 23 1月, 2018 1 次提交
    • T
      env: ENV_IS_IN_FAT improvements · 3cd084d3
      Tuomas Tynkkynen 提交于
      Make it select FS_FAT as well, because if it's not selected, enabling
      ENV_IS_IN_FAT causes a Kconfig warning:
      
      warning: (ENV_IS_IN_FAT) selects FAT_WRITE which has unmet direct dependencies (FS_FAT)
      
      This also allows dropping some code from config_fallbacks.
      
      Also drop the unnecessary help text about having to enable
      CONFIG_FAT_WRITE - Kconfig automatically handles that.
      Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>
      3cd084d3
  10. 16 1月, 2018 1 次提交
  11. 18 12月, 2017 1 次提交
    • K
      rockchip: move CONFIG_ENV_SIZE and CONFIG_ENV_OFFSET to Kconfig · 81f53b0d
      Klaus Goger 提交于
      This commit adds ENV_SIZE and ENV_OFFSET configuration items for
      ARCH_ROCKCHIP, but keeps these non-visible (i.e. not prompt is given).
      With these new items present, the configuration from the header files
      is moved to Kconfig.
      
      Keeping these non-visible is necessary to have the possibility to
      select new default values if CONFIG_IS_IN_* is changed (interactively
      or with oldconfig). Otherwise it will always be set to a previous
      value if used with a prompt.  As an example if we do a defconfig with
      CONFIG_IS_IN_MMC and change it to CONFIG_IS_IN_SPI_FLASH via
      menuconfig, ENV_SIZE and ENV_OFFSET will not be changed to the correct
      values as defconfig will already have set them to the default values
      of CONFIG_IS_IN_MMC in .config.
      Signed-off-by: NKlaus Goger <klaus.goger@theobroma-systems.com>
      Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
      81f53b0d
  12. 21 11月, 2017 1 次提交
  13. 27 10月, 2017 1 次提交
  14. 16 10月, 2017 1 次提交
  15. 15 10月, 2017 1 次提交
  16. 09 9月, 2017 1 次提交
  17. 03 9月, 2017 1 次提交
  18. 20 8月, 2017 1 次提交
  19. 16 8月, 2017 1 次提交
    • S
      env: Convert CONFIG_ENV_IS_IN... to a choice · c1c3fe23
      Simon Glass 提交于
      At present we support multiple environment drivers but there is not way to
      select between them at run time. Also settings related to the position and
      size of the environment area are global (i.e. apply to all locations).
      
      Until these limitations are removed we cannot really support more than one
      environment location. Adjust the location to be a choice so that only one
      can be selected. By default the environment is 'nowhere', meaning that the
      environment exists only in memory and cannot be saved.
      
      Also expand the help for the 'nowhere' option and move it to the top since
      it is the default.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      [trini: Move all of the imply logic to default X if Y so it works again]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      c1c3fe23
  20. 15 8月, 2017 2 次提交