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: AW: [PATCH] Documentation: state: add a little note about modifying a state variable in the frontend
Date: Fri, 6 Nov 2020 08:50:23 +0100	[thread overview]
Message-ID: <5e32bffb-8fc8-c242-a7fc-f3ce15a7cafa@pengutronix.de> (raw)
In-Reply-To: <VI1PR0802MB23341F701DE8044E149A232785ED0@VI1PR0802MB2334.eurprd08.prod.outlook.com>

Hello Matthias,

On 11/6/20 8:14 AM, Matthias Fend wrote:
>> Von: Ahmad Fatoum <a.fatoum@pengutronix.de>
>>
>> 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:
> 
> Thanks for your explanation. Setting a state variable with
> 'state.foo=bar' was actually the way I originally expected.
> Meanwhile, I figured out why I was struggling using things like that.
> All my introduced state variables contained a hyphen in their name.
> And I was not able to set a state variable with 'state.foo-bar=baz' while
> 'nv dev.state.foo-bar=baz' immediately changed the value of
> 'state.foo-bar'. But, as I just learned, with some side effects.
> 
>>
>>   - If you modify the variable from within barebox, it won't be visible
>>     in Linux unless you boot barebox once again.
> 
> I could not verify this behavior. When I change a state variable with
> 'nv dev.state=foo' and then directly boot into Linux (without booting
> barebox again) the 'barebox-state' tool already displays the new value.

Ah, I didn't actually test what I say :D
But makes sense, nv.user sets global.user as well, so why should dev
parameter behave differently.
 
>>   - If you modify the variable from within Linux, nv.dev.state.state.foo
>>     would just overwrite the existing value on the next barebox boot.
> 
> That's true, and of course, not desired.

At least one guess correct ^^

>> 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.
> 
> Right, state, and also it's frontend, does already what it should do and
> as expected.
> Only the hyphen-obstacle caused troubles. So, maybe there is a trick but the fast fix is to simply
> just avoid names that contain hyphens ;)

v2020.10.0 contains 932481a005cc ("commands: setenv: allow use with hush shell"). You can update/
cherry-pick and then use the setenv command instead out of your hush scripts.

Cheers
Ahmad

> 
> Thanks,
>   ~Matthias
> 
> 
>>
>>>   ``state -s`` stores the *state* to the backend device.
>>>
>>
>> --
>> Pengutronix e.K.                           |                             |
>> Steuerwalder Str. 21                       | https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pengutronix.de%2F&amp;data=04%7C01%7CMatthias.Fend%40wolfvision.net%7C264e50c95bc64c72ac6c08d882229f76%7Ce94ec9da9183471e83b351baa8eb804f%7C0%7C0%7C637402432501383585%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=dKzSGReGqacxdJcKZ6eldNiulqmv6%2B8qzQxhijoRbC4%3D&amp;reserved=0  |
>> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
>> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>>

-- 
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-06  7:50 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
2020-11-06  7:14   ` AW: " Matthias Fend
2020-11-06  7:50     ` Ahmad Fatoum [this message]
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=5e32bffb-8fc8-c242-a7fc-f3ce15a7cafa@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