summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTomaz Solc <tomaz.solc@tablix.org>2019-04-16 11:47:48 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2019-04-23 11:51:40 +0200
commit6fcf89d932676951dac05c9c92fcdd54b0ab84a9 (patch)
tree7e295abfe3b4a9d9bcca844c92bb926240e218ea
parent1e8ff7b5025120aedd915dbbdf6b534a446b3827 (diff)
downloadbarebox-6fcf89d932676951dac05c9c92fcdd54b0ab84a9.tar.gz
doc: variables: nv vars are saved automatically.
In recent barebox versions, nv variables are saved automatically upon reset or kernel start (console message "nv variable modified, will save nv variables on shutdown" warns about that). There is no need to explicitly call saveenv. This change was introduced in 3fadbdae. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
-rw-r--r--Documentation/user/variables.rst8
1 files changed, 5 insertions, 3 deletions
diff --git a/Documentation/user/variables.rst b/Documentation/user/variables.rst
index ddfd485..cb1296c 100644
--- a/Documentation/user/variables.rst
+++ b/Documentation/user/variables.rst
@@ -46,9 +46,11 @@ currently running barebox, while changing a nv variable changes the
behaviour persistently over reboots.
nv variables can be created or removed with the :ref:`command_nv`
-command. The nv variables are made persistent using the environment
-facilities of barebox, so a :ref:`command_saveenv` must be issued to store the
-actual values.
+command.
+
+The nv variables are made persistent using the environment facilities of
+barebox. They are saved automatically to the storage medium whenever barebox
+shuts down (that is, a :ref:`command_reset` is issued or a kernel is started).
examples: