From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/8] env: Extract getenv_f() into separate source file
Date: Wed, 26 Sep 2012 13:07:15 +0200 [thread overview]
Message-ID: <5062E1E3.40802@denx.de> (raw)
In-Reply-To: <1348650074-25878-4-git-send-email-sr@denx.de>
On 09/26/2012 11:01 AM, Stefan Roese wrote:
> By extracting getenv_f and envmatch() from cmd_nvedit.c into a
> separate file, getenv_f() can be included easily into the SPL
> binary. With this, SPL boards can now use getenv_f() to read
> environment variables (e.g. to detect if the OS or U-Boot shall
> be executed).
>
> In the approach this is done for env stored in NOR flash, as this
> will be used by an upcoming MPC5200 board port.
This patch is not needed as it seems. I'll post a new version in a short
while that only enables the needed files for SPL_BUILD.
Thanks,
Stefan
next prev parent reply other threads:[~2012-09-26 11:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 9:01 [U-Boot] [PATCH v3 0/8] SPL: Port SPL framework to powerpc Stefan Roese
2012-09-26 9:01 ` [U-Boot] [PATCH v3 1/8] powerpc: Extract EPAPR_MAGIC constants into processor.h Stefan Roese
2012-09-26 9:01 ` [U-Boot] [PATCH v3 2/8] SPL: Port SPL framework to powerpc Stefan Roese
2012-09-28 23:13 ` Scott Wood
2012-09-28 23:32 ` Tom Rini
2012-10-02 10:20 ` Stefan Roese
2012-10-02 20:08 ` Scott Wood
2012-10-04 7:36 ` Stefan Roese
2012-10-04 17:14 ` Scott Wood
2012-10-05 13:15 ` Stefan Roese
2012-10-05 15:22 ` Tom Rini
2012-10-05 16:05 ` Scott Wood
2012-10-05 17:03 ` Stefan Roese
2012-10-05 17:33 ` Tom Rini
2012-09-26 9:01 ` [U-Boot] [PATCH v3 3/8] env: Extract getenv_f() into separate source file Stefan Roese
2012-09-26 11:07 ` Stefan Roese [this message]
2012-09-26 9:01 ` [U-Boot] [PATCH v3 4/8] mpc5200: Add SPL support Stefan Roese
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=5062E1E3.40802@denx.de \
--to=sr@denx.de \
--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