diff options
| author | Doug Anderson <dianders@chromium.org> | 2011-07-13 14:33:32 -0700 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2011-08-29 10:58:55 -0700 |
| commit | e336c3847646d91dfec8baa22f84f429b68c7241 (patch) | |
| tree | a27f844f97dce7b90f9310aa0254926aa4538d66 /README | |
| parent | 45fa8192bffa521a03abffc4b91c850586bbf25a (diff) | |
CHROMIUM: ARM: Allow the FDT to specify that the env loads early.
This is intended for using with the 'legacy' image to allow us to
update the enviroment shipped with the image.
BUG=chromium-os:17196
TEST=With ebuild changes, saw that legacy firmware loaded env and
non-legacy got default.
Change-Id: Iee19df02123ab2502e4803c25c94318b0e834f6d
Reviewed-on: http://gerrit.chromium.org/gerrit/4056
Tested-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 12 |
1 files changed, 7 insertions, 5 deletions
@@ -2537,11 +2537,13 @@ Configuration Settings: cases. This setting can be used to tune behaviour; see lib/hashtable.c for details. -- CONFIG_DELAY_ENVIRONMENT - Normally the environment is loaded when the board is - intialized so that it is available to U-Boot. This inhibits - that so that the environment is not available until - explicitly loaded later by U-Boot code. +- CONFIG_OF_LOAD_ENVIRONMENT + If this variable is defined, U-Boot will use the device tree + setting in "/config/load_env" to decide whether to load the + environment when the board is intialized so that it is + available to U-Boot. If the setting isn't found or is 0, the + environment is not available until explicitly loaded later by + U-Boot code. The following definitions that deal with the placement and management of environment data (variable area); in general, we support the |