mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Matthias Fend <Matthias.Fend@wolfvision.net>,
	"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] Documentation: state: add a little note about modifying a state variable in the frontend
Date: Thu, 5 Nov 2020 21:57:03 +0100	[thread overview]
Message-ID: <1a23e2f4-8b3a-f084-888e-4756d60d92fb@pengutronix.de> (raw)
In-Reply-To: <VI1PR0802MB2334314CB7FA7F0BD64F9C8885EE0@VI1PR0802MB2334.eurprd08.prod.outlook.com>

Hello Matthias,

On 11/5/20 9:16 PM, Matthias Fend wrote:
> Signed-off-by: Matthias Fend <matthias.fend@wolfvision.net>
> ---
>  Documentation/user/state.rst | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/user/state.rst b/Documentation/user/state.rst
> index 78ce24f..d9a8e76 100644
> --- a/Documentation/user/state.rst
> +++ b/Documentation/user/state.rst
> @@ -689,4 +689,5 @@ be accessed like normal shell variables. The ``state`` command is used
>  to save/restore a *state* variable set to the backend device.
>  
>  After initializing the variable can be accessed with ``$state.foo``.
> +To modify the value of a state variable use ``nv dev.state.foo=bar``.

That's wrong. You set the value of a state variable with
state.foo=bar. nv dev.state.state.foo=bar uses the _environment_ to
save a value to write to state.foo on each boot. This means:

 - If you modify the variable from within barebox, it won't be visible
   in Linux unless you boot barebox once again.
 - If you modify the variable from within Linux, nv.dev.state.state.foo
   would just overwrite the existing value on the next barebox boot.

Generally, you should only need to modify nv variables at runtime
for debugging. nv.dev is meant for stuff like nv.dev.eth0.ethaddr=XX:XX:XX:XX:XX:XX,
where you can just hard code a mac address to use, but for state I can't
think of any good use cases at the moment.

>  ``state -s`` stores the *state* to the backend device.
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-11-05 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 20:16 Matthias Fend
2020-11-05 20:57 ` Ahmad Fatoum [this message]
2020-11-06  7:14   ` AW: " Matthias Fend
2020-11-06  7:50     ` Ahmad Fatoum
2020-11-09  9:11     ` Sascha Hauer
2020-11-10 14:09       ` AW: " Matthias Fend

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1a23e2f4-8b3a-f084-888e-4756d60d92fb@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=Matthias.Fend@wolfvision.net \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox