aboutsummaryrefslogtreecommitdiff
path: root/env
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2021-10-21 21:08:52 -0600
committerTom Rini <trini@konsulko.com>2021-11-16 14:35:09 -0500
commit78398652723b6fe743751ffb19d8256b7e3e0a4e (patch)
tree9e86d3aeaf5e46cd0e23bbb8bfc0e6e5406617e0 /env
parent1d192d5bccc6e4b9e7112f720ccc47786694ee39 (diff)
downloadu-boot-78398652723b6fe743751ffb19d8256b7e3e0a4e.zip
u-boot-78398652723b6fe743751ffb19d8256b7e3e0a4e.tar.gz
u-boot-78398652723b6fe743751ffb19d8256b7e3e0a4e.tar.bz2
bootm: Tidy up use of autostart env varWIP/2021-11-16-env-rework
This has different semantics in different places. Go with the bootm method and put it in a common function so that the behaviour is consistent in U-Boot. Update the docs. To be clear, this changes the way that 'bootelf' and standalone boot work. Before, if autostart was set to "fred" or "YES", for example, they would consider that a "yes". This may change behaviour for some boards, but the only in-tree boards which mention autostart use "no" to disable it, which will still work. Signed-off-by: Simon Glass <sjg@chromium.org> Suggested-by: Wolfgang Denk <wd@denx.de>
Diffstat (limited to 'env')
-rw-r--r--env/common.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/env/common.c b/env/common.c
index 208e2ad..ee957c0 100644
--- a/env/common.c
+++ b/env/common.c
@@ -235,6 +235,11 @@ int env_get_yesno(const char *var)
1 : 0;
}
+bool env_get_autostart(void)
+{
+ return env_get_yesno("autostart") == 1;
+}
+
/*
* Look up the variable from the default environment
*/