From 9a7b5d4cdc975f15344c207f9972b2a25b874daf Mon Sep 17 00:00:00 2001 From: Sascha Hauer Date: Wed, 27 Apr 2016 09:04:10 +0200 Subject: Kconfig: Make ENV_HANDLING visible ENV_HANDLING is usable even without explicit loadenv/saveenv command support. Instead of selecting this option from loadenv/saveenv, make this option visible. loadenv/saveenv can then depend on ENV_HANDLING rather than selecting it. This reduces Kconfig dependencies hassles. Signed-off-by: Sascha Hauer --- common/Kconfig | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) (limited to 'common') diff --git a/common/Kconfig b/common/Kconfig index 949c9960b5..a37141e3c7 100644 --- a/common/Kconfig +++ b/common/Kconfig @@ -21,10 +21,6 @@ config HAS_KALLSYMS config HAS_MODULES bool -config ENV_HANDLING - select CRC32 - bool - config HAS_CACHE bool help @@ -646,10 +642,20 @@ config PARTITION source common/partitions/Kconfig +config ENV_HANDLING + select CRC32 + bool "Support environment files storage" + default y if !SHELL_NONE + help + Enabling this option will give you environment files which can be stored + over reboots. The "saveenv" command will store all files under /env/ to + the persistent environment, the "loadenv" command (also executed during + startup) will bring them back. If unsure, say yes. + config DEFAULT_ENVIRONMENT bool default y - select ENV_HANDLING + depends on ENV_HANDLING prompt "Compile in default environment" help Enabling this option will give you a default environment when -- cgit v1.2.3