From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Menon Date: Sat, 23 Mar 2013 10:27:31 -0500 Subject: [U-Boot] [PATCH] omap5: Allow use of a plain text env file In-Reply-To: <514CFF74.2040208@ti.com> References: <1363992223-1628-1-git-send-email-nm@ti.com> <514CFF74.2040208@ti.com> Message-ID: <514DC9E3.7000504@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 03/22/2013 08:03 PM, Tom Rini wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 03/22/2013 06:43 PM, Nishanth Menon wrote: >> 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: Nishanth Menon > > OK, Sricharan is also working on something like this, with a few other > changes as well (Use zImage, load fdt). I suspect we'll be taking > that in. is there a patch posted in u-boot list? or at least an ETA when we might be able to see such a patch? Regards, Nishanth Menon