u-boot.git/env/Kconfig, branch v2018.03

env: sunxi: Enable FAT-based environment support by default

2018-01-27T14:23:32Z

Now that we have everything in place to implement the transition scheme, let's enable it by default. Reviewed-by: Andre Przywara Reviewed-by: Lukasz Majewski Signed-off-by: Maxime Ripard

env: Allow to build multiple environments in Kconfig

2018-01-27T14:23:22Z

Now that we have everything in place in the code, let's allow to build multiple environments backend through Kconfig. Reviewed-by: Andre Przywara Reviewed-by: Lukasz Majewski Reviewed-by: Simon Glass Signed-off-by: Maxime Ripard

env: mmc: depends on the MMC framework

2018-01-27T14:21:57Z

The raw MMC environment directly calls into the MMC framework. Make sure it's enabled before we can select it. Reviewed-by: Simon Glass Signed-off-by: Maxime Ripard Reviewed-by: Jaehoon Chung

env: ENV_IS_IN_FAT improvements

2018-01-22T21:43:31Z

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: Tuomas Tynkkynen

env: enable accessing the environment in an EXT4 partition

2018-01-15T21:28:57Z

For example to store the environment in a file named "/uboot.env" in MMC "0", where partition "1" contains the EXT4 filesystem, the following configs should be added to the board's default config: CONFIG_ENV_IS_IN_EXT4=y CONFIG_ENV_EXT4_DEVICE_AND_PART="0:1" CONFIG_ENV_EXT4_FILE="/uboot.env" CONFIG_ENV_EXT4_INTERFACE="mmc" Signed-off-by: Jorge Ramirez-Ortiz [trini: Fix some line over 80 chars issues] Signed-off-by: Tom Rini

rockchip: move CONFIG_ENV_SIZE and CONFIG_ENV_OFFSET to Kconfig

2017-12-17T23:26:16Z

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: Klaus Goger Reviewed-by: Philipp Tomsich

env: Remove CONFIG_ENV_AES support

2017-11-21T12:43:31Z

This support has been deprecated since v2017.09 due to security issues. We now remove this support. Signed-off-by: Tom Rini

env: x86: braswell: Set ENV_IS_IN_SPI_FLASH as default

2017-10-27T07:13:47Z

Imply does not work for a Kconfig choice. Update ENV_IS_IN_SPI_FLASH to be the default one for Intel Braswell. Signed-off-by: Bin Meng Reviewed-by: Simon Glass

env: Drop CONFIG_ENV_IS_IN_DATAFLASH

2017-10-16T13:42:51Z

Last user of this option went away in commit: fdc7718999 ("board: usb_a9263: Update to support DT and DM") Signed-off-by: Tuomas Tynkkynen

ARM: uniphier: switch to CONFIG_ENV_IS_NOWHERE

2017-10-15T13:32:24Z

The non-volatile storage varies board by board. The default should be NOWHERE. Please choose a proper device via Kconfig. Signed-off-by: Masahiro Yamada