summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorSascha Hauer <s.hauer@pengutronix.de>2019-05-10 18:15:50 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2019-05-10 18:15:50 +0200
commitbac01839b063697200d5b957b652da197b8f0b1d (patch)
tree8b2441ee12fd42abf152d990eda478aaf722e4e9 /Documentation
parent65cfdbebb19f0b1c8d322a3eb9ec464d669a4d3f (diff)
parenta306c1c0bd09e7ee074d113b8a86bd815ef64017 (diff)
downloadbarebox-bac01839b063697200d5b957b652da197b8f0b1d.tar.gz
Merge branch 'for-next/misc'
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/user/state.rst8
-rw-r--r--Documentation/user/variables.rst8
2 files changed, 12 insertions, 4 deletions
diff --git a/Documentation/user/state.rst b/Documentation/user/state.rst
index 07743df..78ce24f 100644
--- a/Documentation/user/state.rst
+++ b/Documentation/user/state.rst
@@ -21,7 +21,13 @@ RAUC_.
.. _RAUC: https://rauc.readthedocs.io/en/latest/
barebox itself uses a *state* driver to access the variables in the
-persistent memory. For the Linux run-time there is a userspace tool_ to do
+persistent memory.
+
+Currently there is only one implementation, enabled by
+``CONFIG_STATE_DRV=y``. Without driver, the state framework will silently
+fail and be non-functional.
+
+For the Linux run-time there is a userspace tool_ to do
the same.
.. _tool: https://git.pengutronix.de/cgit/tools/dt-utils/
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: