From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: New U-boot image format
Date: Tue, 18 Dec 2007 21:11:14 +0100 [thread overview]
Message-ID: <20071218201114.21F5A248AC@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 18 Dec 2007 13:47:29 CST." <476823D1.6040104@freescale.com>
In message <476823D1.6040104@freescale.com> you wrote:
> Wolfgang Denk wrote:
>
> > What good would this do to you? If you run a "dhcp" command with
> > autostart enabled, the image will immediately be autobooted - there
> > will be no place for you to issue a command to do anything with your
> > environment variable.
>
> Wouldn't it be better to run the 'bootcmd' variable? That's how U-Boot has
> always autobooted. I'm sure there are boards out there that need to run some
> commands before booting, and they use bootcmd to do that.
Maybe that's how U-Boot has beeen booted for you in your setup. But
it's just one of a plethora of options, including alternative boot
commands for example selected by failed POST or exceeded boot
counters, etc.
And btw: that's what I'm describing all the time. Consider the
situation where your environment has the following two variable
settings:
autostart=yes
bootcmd=dhcp
Which part of the code would you expect to set the environment
variable (i. e. in which part would you place the hook for the
plugin), and where would you add any code to take notice of this
variable setting?
To mee it seems logical to add the hooks to the "bootm" command code,
which will have to figure out what to do with the individual parts of
the multifile image, and then setting a variable is obviously not
sufficient - you must run some code then.
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
Either one of us, by himself, is expendable. Both of us are not.
-- Kirk, "The Devil in the Dark", stardate 3196.1
next prev parent reply other threads:[~2007-12-18 20:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 16:18 [U-Boot-Users] RFC: New U-boot image format Marian Balakowicz
2007-12-11 16:32 ` [U-Boot-Users] RFC: New U-boot image format - open issues Marian Balakowicz
2007-12-11 19:23 ` [U-Boot-Users] RFC: New U-boot image format Jerry Van Baren
2007-12-11 22:23 ` Wolfgang Denk
2007-12-12 12:38 ` Jerry Van Baren
2007-12-13 22:59 ` Marian Balakowicz
2007-12-13 22:41 ` Marian Balakowicz
2007-12-14 6:17 ` Wolfgang Denk
2007-12-14 21:44 ` T Ziomek
2007-12-19 14:26 ` Marian Balakowicz
2007-12-20 0:50 ` David Gibson
2007-12-20 16:41 ` Scott Wood
2007-12-20 22:25 ` Marian Balakowicz
2007-12-20 22:39 ` Scott Wood
2007-12-21 0:17 ` David Gibson
2007-12-18 15:17 ` Timur Tabi
2007-12-18 15:33 ` Jerry Van Baren
2007-12-18 15:36 ` Timur Tabi
2007-12-18 16:12 ` Wolfgang Denk
2007-12-18 16:17 ` Timur Tabi
2007-12-18 19:42 ` Wolfgang Denk
2007-12-18 19:47 ` Timur Tabi
2007-12-18 20:11 ` Wolfgang Denk [this message]
2007-12-18 20:18 ` Timur Tabi
2007-12-19 14:07 ` Marian Balakowicz
2007-12-20 19:42 ` Wolfgang Denk
2007-12-21 15:04 ` Marian Balakowicz
2007-12-21 15:17 ` Wolfgang Denk
2007-12-21 15:39 ` Marian Balakowicz
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=20071218201114.21F5A248AC@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