summaryrefslogtreecommitdiff
path: root/include/configs/cm-bf561.h
diff options
context:
space:
mode:
authorNishanth Menon <nm@ti.com>2013-04-01 05:52:40 +0000
committerTom Rini <trini@ti.com>2013-04-08 11:29:05 -0400
commit78fd004107cbba4e71d04c0546b22a787cb4c376 (patch)
treec1b8021edfe85d1988bf437508495b2a8ccf429a /include/configs/cm-bf561.h
parentd3501ed584d7c00dca0eccd3c009aa3924e2fa3c (diff)
downloadu-boot-imx-78fd004107cbba4e71d04c0546b22a787cb4c376.zip
u-boot-imx-78fd004107cbba4e71d04c0546b22a787cb4c376.tar.gz
u-boot-imx-78fd004107cbba4e71d04c0546b22a787cb4c376.tar.bz2
omap5: Allow use of a plain text env file
For production systems it is better to use script images since they are protected by checksums and carry valuable information like name and timestamp. Also, you can't validate the content passed to env import. But for development, it is easier to use the env import command and plain text files instead of script-images. Since both OMAP5evm/uevm boards are used primarily for development, we allow U-Boot to load env var from a text file in case that an boot.scr script-image is not present. The variable uenvcmd (if existent) will be executed (using run) after uEnv.txt was loaded. If uenvcmd doesn't exist the default boot sequence will be started. Inspired by commit: d70f54808dfa83b574e1239c3eccbcf3317343e1 (omap4: allow the use of a plain text env file instead boot scripts) Signed-off-by: Sricharan R <r.sricharan@ti.com> Signed-off-by: Nishanth Menon <nm@ti.com> Tested-by: Sricharan R <r.sricharan@ti.com>
Diffstat (limited to 'include/configs/cm-bf561.h')
0 files changed, 0 insertions, 0 deletions