From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Standalone application after powerup
Date: Fri, 10 Oct 2008 11:35:06 +0200 [thread overview]
Message-ID: <20081010093506.7FEB18227B3F@gemini.denx.de> (raw)
In-Reply-To: <19914708.post@talk.nabble.com>
Dear "Nagesh.ML",
In message <19914708.post@talk.nabble.com> you wrote:
>
> What could be the possible solution to include the standalone application in
> my board powerup sequence?
This depends on where you want to include it. I think it is obvious
that SA applications require a substantial amount of U-Boot
infrastructure to be running. By design, they are intended to be
called only when any other interactive command can be exectuted. If
you know exactly what you are doing, you may run them a little
earlier, but probbaly not much.
Me recommendation is: if you want to run SA applications early, you
can do this from the "preboot" hook. Any earlier point may or may not
work, and especially there is no guarantee that this will not break
in any future versions of U-Boot.
Keep in mind what SA applications are used for - especailly, they are
NOT intended to sneak in propriatary initialization code in early
boot stages, and this is about the only reason I can imagine to use
them in that early.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
HR Manager to job candidate "I see you've had no computer training.
Although that qualifies you for upper management, it means you're
under-qualified for our entry level positions."
prev parent reply other threads:[~2008-10-10 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 9:08 [U-Boot] Standalone application after powerup Nagesh.ML
2008-10-10 9:35 ` Wolfgang Denk [this message]
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=20081010093506.7FEB18227B3F@gemini.denx.de \
--to=wd@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