Introduce non volatile device variables

[Sascha Hauer <s.hauer@pengutronix.de>]

So far we have non volatile (nv) variables which keep their values
over reboots. This series extends the concept to device
parameters. This can be used to configure devices and to preserve
the configuration over reboots. The non volatile device variables
are implemented as regular nv variables with a special namespace.
Every nv variable with the form "nv.dev.<devname>.<paramname>"
acts on the parameter <paramname> of the device named <devname>.

With this for example mtd partitioning can be stored:

 nv dev.nand0.partitions=4M(barebox),-(root)

Or videomodes:

 nv dev.fb0.mode="1280x1024"

It's planned to also replace the current network settings in /env/network/*
with this mechanism, but additional patches are necessary to make
dhcp work.

This is another step to make scripts in barebox simpler and sometimes
unnecessary.

Sascha

----------------------------------------------------------------
Sascha Hauer (3):
      nvvar: Simplify by using nv_set()
      nvvar: Simplify by using dev_set_param()
      Introduce non volatile device variables

 Documentation/user/variables.rst |  18 +++++
 common/globalvar.c               | 151 ++++++++++++++++++++++++++++++++-------
 include/globalvar.h              |   6 ++
 lib/parameter.c                  |   3 +
 4 files changed, 154 insertions(+), 24 deletions(-)

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