From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] Add option -r to env import to allow import of text files with CRLF as line endings
Date: Thu, 14 Aug 2014 13:51:21 -0600 [thread overview]
Message-ID: <53ED1339.7050905@wwwdotorg.org> (raw)
In-Reply-To: <53ED1047.3000607@ahsoftware.de>
On 08/14/2014 01:38 PM, Alexander Holler wrote:
> Am 14.08.2014 17:49, schrieb Stephen Warren:
>> On 08/14/2014 02:25 AM, Alexander Holler wrote:
>
>>> As I've just remembered where I did see your name before, the config for
>>> the rpi (as found in 2004.04) misses the uenvcmd. That's necessary to
>>> execute commands when using uEnv.txt.
>>>
>>> It's easily done with something like the following:
>>>
>>> "env import -t -r $loadaddr
>>> $filesize;" \
>>> "if test -n \"$uenvcmd\"; then " \
>>> "echo \"Running uenvcmd
>>> ...\";" \
>>> "run uenvcmd;" \
>>> "fi;" \
>>
>> My intention was that uEnv.txt be used to set up environment variables,
>> not to allow its use for custom scripts.
>>
>
> Sure. In most cases changing the predefined available variables is
> enough. But it's a very hand option if someone wants or needs to do
> stuff which can't be done by just changing some environment variables
> (one never knows what ideas people will have).
For such presumably non-standard things, why can't the user simply edit
$bootcmd, and pre-pend whatever they want?
next prev parent reply other threads:[~2014-08-14 19:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 15:49 [U-Boot] [PATCH 0/4] Add option -r to env import to allow import of text files with CRLF as line endings Alexander Holler
2014-07-14 15:49 ` [U-Boot] [PATCH 1/4] " Alexander Holler
2014-07-22 19:23 ` [U-Boot] [U-Boot, " Tom Rini
2014-07-30 22:47 ` [U-Boot] [PATCH " Stephen Warren
2014-07-31 19:51 ` Tom Rini
2014-07-31 19:57 ` Stephen Warren
2014-08-14 8:25 ` Alexander Holler
2014-08-14 15:49 ` Stephen Warren
2014-08-14 18:41 ` Robert Nelson
2014-08-14 19:38 ` Tom Rini
2014-08-14 19:50 ` Stephen Warren
2014-08-14 20:53 ` Tom Rini
2014-08-14 21:05 ` Alexander Holler
2014-08-14 21:35 ` Stephen Warren
2014-08-14 21:44 ` Alexander Holler
2014-08-14 19:38 ` Alexander Holler
2014-08-14 19:51 ` Stephen Warren [this message]
2014-08-14 19:59 ` Alexander Holler
2014-08-14 20:08 ` Stephen Warren
2014-08-14 20:39 ` Alexander Holler
2014-08-01 12:08 ` Wolfgang Denk
2014-08-02 21:09 ` Alexander Holler
2014-08-03 16:38 ` Alexander Holler
2014-08-03 17:51 ` Wolfgang Denk
2014-08-04 6:47 ` Alexander Holler
2014-08-04 7:00 ` Alexander Holler
2014-08-04 10:00 ` Måns Rullgård
2014-08-04 19:18 ` Alexander Holler
2014-08-06 6:43 ` Wolfgang Denk
2014-08-06 10:02 ` Alexander Holler
2014-08-06 10:28 ` Alexander Holler
2014-08-06 10:44 ` Måns Rullgård
2014-08-06 11:18 ` Alexander Holler
2014-08-06 11:48 ` Alexander Holler
2014-08-03 17:47 ` Wolfgang Denk
2014-07-14 15:49 ` [U-Boot] [PATCH 2/4] omap3_beagle: handle import of environments in " Alexander Holler
2014-07-22 19:23 ` [U-Boot] [U-Boot, " Tom Rini
2014-07-14 15:49 ` [U-Boot] [PATCH 3/4] am335x_evm: " Alexander Holler
2014-07-22 19:23 ` [U-Boot] [U-Boot, " Tom Rini
2014-07-14 15:49 ` [U-Boot] [PATCH 4/4] rpi_b: " Alexander Holler
2014-07-22 19:23 ` [U-Boot] [U-Boot, " Tom Rini
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=53ED1339.7050905@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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