All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Intent of CONFIG_NAND_ENV_DST?
Date: Mon, 19 Dec 2011 12:57:21 -0600	[thread overview]
Message-ID: <4EEF8911.7040004@freescale.com> (raw)
In-Reply-To: <CA+M6bXkSwoOBgBuj5E_196G2-9hq-V41qNQ5Dn=Fav7OamYzGA@mail.gmail.com>

On 12/19/2011 11:58 AM, Tom Rini wrote:
> Hey all,
> 
> I'm attempting to use CONFIG_NAND_ENV_DST work, and I'm wondering it
> what I see as the intent of the option is the real intent as it's not
> working without patches, but perhaps I'm just using it wrong.  What
> I'm trying to have done is that if the above is set, SPL will read the
> environment from NAND into CONFIG_NAND_ENV_DST (nand_spl/ code does
> this, today) and once U-Boot itself is fired up, env_init will see
> we've been given a real environment and go.  But what happens now is
> that there's no special case of env_relocate_spec that knows our
> current pointer is fine and just needs to populate the table.

Hmm... so it will unnecessarily reread the environment, discarding any
variables that have been modified before then.  That should be fixed (I
think we just need to add CONFIG_NAND_ENV_DST to the ENV_IS_EMBEDDED
ifdef in env_relocate_spec, as was done in env_init), though the primary
intent was simply to get early read access to variables such as serial
baud -- for that, it should already work, right?

-Scott

  reply	other threads:[~2011-12-19 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19 17:58 [U-Boot] Intent of CONFIG_NAND_ENV_DST? Tom Rini
2011-12-19 18:57 ` Scott Wood [this message]
2011-12-19 19:18   ` 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=4EEF8911.7040004@freescale.com \
    --to=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.