1. 27 1月, 2018 3 次提交
  2. 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
  3. 16 1月, 2018 1 次提交
  4. 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
  5. 21 11月, 2017 1 次提交
  6. 27 10月, 2017 1 次提交
  7. 16 10月, 2017 1 次提交
  8. 15 10月, 2017 1 次提交
  9. 09 9月, 2017 1 次提交
  10. 03 9月, 2017 1 次提交
  11. 20 8月, 2017 1 次提交
  12. 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
  13. 15 8月, 2017 2 次提交