expo: doc: Update documentation for persistent settings

Add mention of persistent settings in the documentation.

Signed-off-by: Simon Glass <sjg@chromium.org>

diff --git a/doc/develop/cedit.rst b/doc/develop/cedit.rst
index 8f0a554ae91808aff7de04b56a6b59018d3ae081..63dff9d3f1404489977cebbcbe78bdbb91b7be5e 100644 (file)
--- a/doc/develop/cedit.rst
+++ b/doc/develop/cedit.rst
@@ -152,3 +152,18 @@ Themes
 
 The configuration editor uses simple expo themes. The theme is read from
 `/bootstd/cedit-theme` in the devicetree.
+
+
+Reading and writing settings
+----------------------------
+
+Cedit provides several options for persistent settings:
+
+- Writing an FDT file to a filesystem
+- Writing to U-Boot's environment variables, which are then typically stored in
+  a persistent manner
+- Writing to CMOS RAM registers (common on x86 machines)
+
+For now, reading and writing settings is not automatic. See the
+:doc:`../usage/cmd/cedit` for how to do this on the command line or in a
+script.

diff --git a/doc/develop/expo.rst b/doc/develop/expo.rst
index 61b6855c72f48a77645093d2ec602d48435680e1..f13761995d3f4446f8bc1f99ba5a1a5f8b37fa22 100644 (file)
--- a/doc/develop/expo.rst
+++ b/doc/develop/expo.rst
@@ -485,7 +485,6 @@ Some ideas for future work:
 - Support unicode
 - Support curses for proper serial-terminal menus
 - Add support for large menus which need to scroll
-- Add support for reading and writing configuration settings with cedit
 - Update expo.py tool to check for overlapping names and CMOS locations
 
 .. Simon Glass <sjg@chromium.org>