public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] environment access before relocation does not work on (some) arm
Date: Fri, 29 Jun 2012 11:42:15 +0200	[thread overview]
Message-ID: <4FED7877.2020505@esd.eu> (raw)

Hi,

I just noticed that using getenv (and friends)
does not work on ARM (namely i.MX28) from board_init_f()
after running through the init_sequence.

So getenv_ulong() always returns the given default.
So the baudrate on affected boards is always set by CONFIG_BAUDRATE
and cannot be adjusted by the baudrate env variable and so on.
Environment access before relocation is required for some functions:
pram, fdtcontroladdr, baudrate, ...

Env access does not work before env_relocate() in board_init_r().

Didn't this behave different sometimes before? Even after the big
env rework?

Matthias

             reply	other threads:[~2012-06-29  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29  9:42 Matthias Fuchs [this message]
2012-06-29 11:26 ` [U-Boot] environment access before relocation does not work on (some) arm Wolfgang Denk
2012-07-03 14:51   ` Matthias Fuchs
2012-07-03 18:04     ` Wolfgang Denk

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=4FED7877.2020505@esd.eu \
    --to=matthias.fuchs@esd.eu \
    --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