mirror of
https://github.com/u-boot/u-boot.git
synced 2024-11-25 05:04:23 +08:00
expo: doc: Update documentation for persistent settings
Add mention of persistent settings in the documentation. Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
parent
cfc402db39
commit
84b08afcbb
@ -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.
|
||||
|
@ -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>
|
||||
|
Loading…
Reference in New Issue
Block a user