From a871af2d5a59c26d4ff7e60530a7afce0742e6f0 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Pali=20Roh=C3=A1r?= Date: Sun, 7 Aug 2022 21:06:04 +0200 Subject: [PATCH] hwconfig: Allow to use restricted env MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit During early boot phase GD_FLG_ENV_READY is not set but env_get() may work when env is ready in restricted mode. Do not fail with error message "WARNING: Calling __hwconfig without a buffer and before environment is ready" when env is already working by checking for ENV_VALID flag. Signed-off-by: Pali Rohár --- common/hwconfig.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/hwconfig.c b/common/hwconfig.c index 43566b81bd..cac0b6348f 100644 --- a/common/hwconfig.c +++ b/common/hwconfig.c @@ -78,7 +78,7 @@ static const char *__hwconfig(const char *opt, size_t *arglen, /* if we are passed a buffer use it, otherwise try the environment */ if (!env_hwconfig) { - if (!(gd->flags & GD_FLG_ENV_READY)) { + if (!(gd->flags & GD_FLG_ENV_READY) && gd->env_valid != ENV_VALID) { printf("WARNING: Calling __hwconfig without a buffer " "and before environment is ready\n"); return NULL; -- 2.39.5