diff options
author | Simon Glass <sjg@chromium.org> | 2023-07-31 06:01:46 +0300 |
---|---|---|
committer | Bin Meng <bmeng.cn@gmail.com> | 2023-08-09 18:31:12 +0300 |
commit | 63af90e7f0cab3b5197c19744f5e807ebc325c81 (patch) | |
tree | 2d264d8c4e98d5cb0e93fd4731aedcc67df877ae | |
parent | 5e541a05f70296dbad07fc1f4e8678ad207bb476 (diff) | |
download | u-boot-63af90e7f0cab3b5197c19744f5e807ebc325c81.tar.xz |
env: Explain how to use #include files in text environment
Provide documentation on how to share common settings among boards.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> # Intel Edison
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
-rw-r--r-- | doc/usage/environment.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/usage/environment.rst b/doc/usage/environment.rst index 91dc07b17b..c6439dde66 100644 --- a/doc/usage/environment.rst +++ b/doc/usage/environment.rst @@ -81,6 +81,12 @@ Example:: echo CONFIG_SYS_BOARD boot failed - please check your image echo Load address is CONFIG_SYS_LOAD_ADDR +Settings which are common to a group of boards can use #include to bring in +a common file in the `include/env` directory, containing environment +settings. For example:: + + #include <env/ti/mmc.env> + If CONFIG_ENV_SOURCE_FILE is empty and the default filename is not present, then the old-style C environment is used instead. See below. |