From patchwork Tue Jan 28 10:51:06 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "J, KEERTHY" X-Patchwork-Id: 240393 List-Id: U-Boot discussion From: j-keerthy at ti.com (Keerthy) Date: Tue, 28 Jan 2020 16:21:06 +0530 Subject: [PATCH v5 01/10] env: nowhere: set default enviroment In-Reply-To: <20200128105115.21604-1-j-keerthy@ti.com> References: <20200128105115.21604-1-j-keerthy@ti.com> Message-ID: <20200128105115.21604-2-j-keerthy@ti.com> In case only CONFIG_ENV_IS_NOWHERE without any of the memory based configs like CONFIG_ENV_IS_IN_MMC the env_set function fails as the gd->flags & GD_FLG_ENV_READY check fails. Set default enviroment so that set_env calls succeed when only ENV_IS_NOWHERE set. Signed-off-by: Keerthy Reviewed-by: Tom Rini --- env/nowhere.c | 1 + 1 file changed, 1 insertion(+) diff --git a/env/nowhere.c b/env/nowhere.c index f5b0a17652..70c3b3e011 100644 --- a/env/nowhere.c +++ b/env/nowhere.c @@ -23,6 +23,7 @@ static int env_nowhere_init(void) { gd->env_addr = (ulong)&default_environment[0]; gd->env_valid = ENV_INVALID; + env_set_default(NULL, 0); return 0; }