From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] uboot: add support for a uEnv.txt file
Date: Fri, 13 Sep 2013 09:01:34 +0200 [thread overview]
Message-ID: <20130913090134.2b05d3e8@skate> (raw)
In-Reply-To: <1379029303-17804-1-git-send-email-rjbarnet@rockwellcollins.com>
Dear Ryan Barnett,
On Thu, 12 Sep 2013 18:41:43 -0500, Ryan Barnett wrote:
> Some boards in u-boot support the ability to modify the environment
> by placing a plain text file as uEnv.txt in the root of the partition
> of an SD card. For the extact placement of where the uEnv.txt should
> be, consult your u-boot environment. Your board supports this
> overwriting of environment variables if "loadbootenv" and
> "importbootenv" are defined in the board's environment.
loadbootenv and importbootenv are just U-Boot scripts that are specific
to certain board configurations.
All what loadbootenv does it load a file into memory, and all what
importbootenv does is call 'env import -t <addr> <size>' to load the
environment into U-Boot.
So I don't think we should be mentioning loadbootenv and importbootenv
here.
However, what I'm really wondering if is we really need this. After
all, this is all about copying a text file to $(BINARIES_DIR),
something a post-build or a post-image script can do perfectly fine. I
mean, there's nothing U-Boot specific involved here, it's just a plain
'cp'. Therefore, I'm not sure we need this at all, but I am open to
discussion on this.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-13 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 23:41 [Buildroot] [PATCH 1/1] uboot: add support for a uEnv.txt file Ryan Barnett
2013-09-13 2:13 ` Danomi Manchego
2013-09-13 7:01 ` Thomas Petazzoni [this message]
2013-09-13 14:36 ` Ryan Barnett
2013-09-13 20:42 ` Arnout Vandecappelle
2013-09-13 20:57 ` Ryan Barnett
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=20130913090134.2b05d3e8@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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