Skip to content
Snippets Groups Projects
  • Simon Glass's avatar
    86b9c3e4
    env: Allow U-Boot scripts to be placed in a .env file · 86b9c3e4
    Simon Glass authored and Tom Rini's avatar Tom Rini committed
    
    At present U-Boot environment variables, and thus scripts, are defined
    by CONFIG_EXTRA_ENV_SETTINGS. It is painful to add large amounts of text
    to this file and dealing with quoting and newlines is harder than it
    should be. It would be better if we could just type the script into a
    text file and have it included by U-Boot.
    
    Add a feature that brings in a .env file associated with the board
    config, if present. To use it, create a file in a board/<vendor>
    directory, typically called <board>.env and controlled by the
    CONFIG_ENV_SOURCE_FILE option.
    
    The environment variables should be of the form "var=value". Values can
    extend to multiple lines. See the README under 'Environment Variables:'
    for more information and an example.
    
    In many cases environment variables need access to the U-Boot CONFIG
    variables to select different options. Enable this so that the environment
    scripts can be as useful as the ones currently in the board config files.
    This uses the C preprocessor, means that comments can be included in the
    environment using /* ... */
    
    Also support += to allow variables to be appended to. This is needed when
    using the preprocessor.
    
    Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    Reviewed-by: default avatarMarek Behún <marek.behun@nic.cz>
    Tested-by: default avatarMarek Behún <marek.behun@nic.cz>
    86b9c3e4
    History
    env: Allow U-Boot scripts to be placed in a .env file
    Simon Glass authored and Tom Rini's avatar Tom Rini committed
    
    At present U-Boot environment variables, and thus scripts, are defined
    by CONFIG_EXTRA_ENV_SETTINGS. It is painful to add large amounts of text
    to this file and dealing with quoting and newlines is harder than it
    should be. It would be better if we could just type the script into a
    text file and have it included by U-Boot.
    
    Add a feature that brings in a .env file associated with the board
    config, if present. To use it, create a file in a board/<vendor>
    directory, typically called <board>.env and controlled by the
    CONFIG_ENV_SOURCE_FILE option.
    
    The environment variables should be of the form "var=value". Values can
    extend to multiple lines. See the README under 'Environment Variables:'
    for more information and an example.
    
    In many cases environment variables need access to the U-Boot CONFIG
    variables to select different options. Enable this so that the environment
    scripts can be as useful as the ones currently in the board config files.
    This uses the C preprocessor, means that comments can be included in the
    environment using /* ... */
    
    Also support += to allow variables to be appended to. This is needed when
    using the preprocessor.
    
    Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    Reviewed-by: default avatarMarek Behún <marek.behun@nic.cz>
    Tested-by: default avatarMarek Behún <marek.behun@nic.cz>
config.mk 2.15 KiB