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. --- Documentation/user/variables.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/user/variables.rst b/Documentation/user/variables.rst index ddfd48574..cb1296c06 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: -- 2.11.0 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
