diff options
author | Simon Glass <sjg@chromium.org> | 2023-08-14 16:40:39 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2023-08-25 13:54:33 -0400 |
commit | 84b08afcbb8f8b4402b940d87bf5822984eedb3d (patch) | |
tree | 8a62bb1cda41f5fb2ff2cb0211e927e45645e18a | |
parent | cfc402db3954d7c852c322b232ad6d8842af6bf1 (diff) | |
download | u-boot-84b08afcbb8f8b4402b940d87bf5822984eedb3d.zip u-boot-84b08afcbb8f8b4402b940d87bf5822984eedb3d.tar.gz u-boot-84b08afcbb8f8b4402b940d87bf5822984eedb3d.tar.bz2 |
expo: doc: Update documentation for persistent settingsWIP/2023-08-25-add-persistent-config-editor-via-expo
Add mention of persistent settings in the documentation.
Signed-off-by: Simon Glass <sjg@chromium.org>
-rw-r--r-- | doc/develop/cedit.rst | 15 | ||||
-rw-r--r-- | doc/develop/expo.rst | 1 |
2 files changed, 15 insertions, 1 deletions
diff --git a/doc/develop/cedit.rst b/doc/develop/cedit.rst index 8f0a554..63dff9d 100644 --- 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 61b6855..f137619 100644 --- 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> |