From 6fcf89d932676951dac05c9c92fcdd54b0ab84a9 Mon Sep 17 00:00:00 2001 From: Tomaz Solc Date: Tue, 16 Apr 2019 11:47:48 +0200 Subject: 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 --- Documentation/user/variables.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'Documentation') diff --git a/Documentation/user/variables.rst b/Documentation/user/variables.rst index ddfd485740..cb1296c06d 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: -- cgit v1.2.3 From 17ab16933959bf8722c6cb353f31fc06926e2ad4 Mon Sep 17 00:00:00 2001 From: Moritz Augsburger Date: Tue, 23 Apr 2019 21:56:08 +0200 Subject: doc: clarify state framework driver requirement --- Documentation/user/state.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'Documentation') diff --git a/Documentation/user/state.rst b/Documentation/user/state.rst index 07743df0cb..78ce24f9ed 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/ -- cgit v1.2.3