summaryrefslogtreecommitdiff
path: root/board
diff options
context:
space:
mode:
authorJavier Martinez Canillas <javier@dowhile0.org>2013-01-07 03:51:20 +0000
committerTom Rini <trini@ti.com>2013-02-07 10:36:25 -0500
commitd70f54808dfa83b574e1239c3eccbcf3317343e1 (patch)
tree70d1e043f50616df4b1f6f7e8972c5b0dd42c818 /board
parent9d4f542123a4ec7557e40a6944c93cbae9242eb3 (diff)
downloadu-boot-imx-d70f54808dfa83b574e1239c3eccbcf3317343e1.zip
u-boot-imx-d70f54808dfa83b574e1239c3eccbcf3317343e1.tar.gz
u-boot-imx-d70f54808dfa83b574e1239c3eccbcf3317343e1.tar.bz2
omap4: allow the use of a plain text env file instead boot scripts
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 OMAP4 supported boards (Panda and TI SDP4430) are used primarily for development, this patch allows 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. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk> Acked-by: Nishanth Menon <nm@ti.com>
Diffstat (limited to 'board')
0 files changed, 0 insertions, 0 deletions