From: Sricharan R <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap5: Allow use of a plain text env file
Date: Mon, 25 Mar 2013 10:16:23 +0530 [thread overview]
Message-ID: <514FD69F.9040703@ti.com> (raw)
In-Reply-To: <514FB8EA.4080602@gmail.com>
On Monday 25 March 2013 08:09 AM, Nishanth Menon wrote:
> On 03/23/2013 11:20 PM, Sricharan R wrote:
>> Hi Nishanth,
>>
>> On Saturday 23 March 2013 08:57 PM, Nishanth Menon wrote:
>>> 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 <nm@ti.com> In fac
>>>>
>>>> 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
>>>
>> I added this in the series.
>>
>> http://www.mail-archive.com/u-boot at lists.denx.de/msg109030.html
> thanks.
> Regards,
> Nishanth Menon
>
In fact i added my version of this patch. Same functional change.
I will add your patch instead of mine, given that you posted before mine.
Regards,
Sricharan
prev parent reply other threads:[~2013-03-25 4:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 22:43 [U-Boot] [PATCH] omap5: Allow use of a plain text env file Nishanth Menon
2013-03-23 0:23 ` Wolfgang Denk
2013-03-23 1:07 ` Tom Rini
2013-03-23 1:03 ` Tom Rini
2013-03-23 15:27 ` Nishanth Menon
2013-03-24 4:20 ` Sricharan R
2013-03-25 2:39 ` Nishanth Menon
2013-03-25 4:46 ` Sricharan R [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=514FD69F.9040703@ti.com \
--to=r.sricharan@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox