From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM POST Tests.
Date: Wed, 20 Jul 2011 14:32:25 +0200 [thread overview]
Message-ID: <4E26CAD9.3090204@keymile.com> (raw)
In-Reply-To: <20110720122055.87A3C1579DF2@gemini.denx.de>
On 07/20/2011 02:20 PM, Wolfgang Denk wrote:
> Dear Valentin Longchamp,
>
> In message <4E26B523.3070609@keymile.com> you wrote:
>>
>> I have done a little bit of profiling this morning, and the main culprit is the
>> call to getenv_f in post_get_flags for the four environment variables:
>>
>> "post_poweron", "post_normal", "post_slowtest" "post_critical"
>>
>> This is extremly slow on my system (before relocation). The goal of these env
>
> Are you by chance reading the environment from I2C attached EEPROM or
> so? This is indeed a speed killer.
Yeah I had just figured that out by myself: our environement variables are in an
I2C EEPROM, so every read is extremely slow at this poin in the boot process.
For the second POST run (from RAM this time), the environment is then in RAM
(thanks to env_relocate) and thus the calls to getenv_f much quicker.
>
>> variables is, I guess, to define the name of the tests that have to be run for
>> each post level, right ? Is this the only way to define which tests are to be run ?
>
> To define the tests to be run, and the reaction that is needed if a
> test fails.
>
> If your environment accesses are so slow, you should fix that anyway.
>
We are currently planning to move away from I2C EEPROM for environment (for
future hardware), but what would you advise me to do for our current hardware
where the environment is in this EEPROM ?
--
Valentin Longchamp
Embedded Software Engineer
Hardware and Chip Integration
______________________________________
KEYMILE AG
Schwarzenburgstr. 73
CH-3097 Liebefeld
Phone +41 31 377 1318
Fax +41 31 377 1212
valentin.longchamp at keymile.com
www.keymile.com
______________________________________
KEYMILE: A Specialist as a Partner
next prev parent reply other threads:[~2011-07-20 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 12:59 [U-Boot] ARM POST Tests sreekumar.sivakumar at wipro.com
2011-07-15 8:13 ` Heiko Schocher
2011-07-19 15:29 ` Valentin Longchamp
2011-07-19 18:45 ` Wolfgang Denk
2011-07-20 10:59 ` Valentin Longchamp
2011-07-20 12:20 ` Wolfgang Denk
2011-07-20 12:32 ` Valentin Longchamp [this message]
2011-07-20 13:15 ` Wolfgang Denk
2011-07-19 18:18 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2014-02-06 13:14 [U-Boot] arm post tests shobin b
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=4E26CAD9.3090204@keymile.com \
--to=valentin.longchamp@keymile.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox