On 08/05/17 15:45, Ian Abbott wrote:
As a related follow-up, this code in globalvar_add_simple() looks a bit
strange:
if (value)
dev_set_param(&global_device, name, value);
globalvar_nv_sync(name);
If you set a new global variable with a specified value and there is an
existing nv variable of the same name, the global variable will be set
to the value of the nv variable, rather than the specified value:
barebox@xxxx:/ nv -r quux
barebox@xxxx:/ global -r quux
barebox@xxxx:/ nv quux=foo
barebox@xxxx:/ global quux=bar
barebox@xxxx:/ echo ${global.quux}
foo
That was with 2017.05.0. I'll check the behaviour with Sascha's patch
shortly.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@xxxxxxxxx> )=-
-=( Web: http://www.mev.co.uk/ )=-
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
