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: Tue, 03 Jul 2012 16:51:40 +0200 [thread overview]
Message-ID: <4FF306FC.9040305@esd.eu> (raw)
In-Reply-To: <20120629112655.631D02000C7@gemini.denx.de>
Hi,
On 29.06.2012 13:26, Wolfgang Denk wrote:
> Dear Matthias Fuchs,
>
> In message <4FED7877.2020505@esd.eu> you wrote:
>>
>> 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.
>
> This is normal, and documented. Before relocation, you must not use
> getenv().
Yes, I am aware of this. I even think that the getenv() implementation
falls back to getenv_f() before relocation.
>
>> Env access does not work before env_relocate() in board_init_r().
>
> It does, but you have to play by the rules, i. e. use getenv_f()
> instead.
Yes, I did not care about where my env comes from :-) So env_sf.c does
not support an early env at all. Running on an i.MX28 with env in a SPI
flash I probably need SPI support in my SPL and an improved env_sf.c.
... and all this to get CONFIG_PRAM working in arch/arm/lib/board.c.
So I will stuck at using a constant pram value for the moment. This works.
>
>> Didn't this behave different sometimes before? Even after the big
>> env rework?
>
> No. The use of getenv() before relocation has never been supported.
> It may have worked (by pure chance) on some systems, but that's all.
Of course. My question was not very precise.
Matthias
>
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2012-07-03 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 9:42 [U-Boot] environment access before relocation does not work on (some) arm Matthias Fuchs
2012-06-29 11:26 ` Wolfgang Denk
2012-07-03 14:51 ` Matthias Fuchs [this message]
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=4FF306FC.9040305@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