From: Tom Rini <trini@ti.com>
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 16:53:49 -0400 [thread overview]
Message-ID: <20140814205349.GI19374@bill-the-cat> (raw)
In-Reply-To: <53ED1307.9020207@wwwdotorg.org>
On Thu, Aug 14, 2014 at 01:50:31PM -0600, Stephen Warren wrote:
[snip]
> uenv.txt is the opposite; it's very U-Boot specific, and more about
> internal implementation details of U-Boot. In particular, I only see
> a use-case for uenv.txt on systems that have nowhere to store the
> U-Boot environment other than in some filesystem. That's the reason
> the RPi port loads uenv.txt, so the environment can be modified
> somehow. Perhaps there's an ENV_IS_IN_FAT that could be used instead
> on the Pi? For example, none of the Tegra boards use uEnv.txt since
> "saveenv" to flash works there.
Even with ENV_IS_IN_FAT you need to be in U-Boot to modify the
environment (fw_setenv/printenv should be adaptable easily enough I
would hope, but aren't today). uEnv.txt is the way for a user to pop
the SD card into their PC, tweak the env as needed (or fiddle some
bits), eject the card and boot their target.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140814/b1391755/attachment.pgp>
next prev parent reply other threads:[~2014-08-14 20:53 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 [this message]
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
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=20140814205349.GI19374@bill-the-cat \
--to=trini@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