public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] zImage on ARM
Date: Thu, 09 Sep 2010 19:22:21 +0200	[thread overview]
Message-ID: <20100909172221.37AB41506AA@gemini.denx.de> (raw)
In-Reply-To: <20100909112816.7bd37645@schlenkerla.am.freescale.net>

Dear Scott Wood,

In message <20100909112816.7bd37645@schlenkerla.am.freescale.net> you wrote:
>
> Then why does u-boot only support certain calling conventions with
> certain image formats?

The "bootm" command supports only images it understands.

> So in other words, for booting an OS, U-Boot insists on particular
> image formats.

No, it does not. You can provide the OS in a  U-Boot specific
standard way (FIT or legacy image format), you can provide it in a
system independent format (ELF), or you can provide it in a "simple
binary" format (to be used with "go").

> > The go command takes arguments, which get passed to the started
> > application in the standard C calling convention. It is up to the
> > image to interpret these, then.
> 
> It passes *text* arguments supplied by the command line, in argc/argv
> format.  Which seems like it's not intended to be an arbitrary image
> loading command, but rather a facility to execute things that look and
> feel like shell commands.

It's the standard C calling convention, i. e. pretty common standard.

> Yes.  "simple" refers to the image format, not the calling convention.

As I explained before: feel free to craft your own specific boot
command from the building blocks provided.

There is a standard way of doing this; if you don't want to use it
it's fine with me. Define a "bootz" command or whatever you like.

Don't expect me to scratch your itches, though. In all the past 10
years when I've been working with PPCBoot and U-Boot I never felt the
need to boot a zImage.

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
Due to lack of disk space, this fortune database has been discontinued.

  reply	other threads:[~2010-09-09 17:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 21:43 [U-Boot] zImage on ARM Steve Sakoman
2010-09-02 22:45 ` Paulraj, Sandeep
2010-09-02 22:45 ` Wolfgang Denk
2010-09-03 21:47   ` Loïc Minier
2010-09-07 23:04     ` Wolfgang Denk
2010-09-08 20:23       ` Scott Wood
2010-09-08 20:32         ` Wolfgang Denk
2010-09-08 20:34           ` Scott Wood
2010-09-08 20:43             ` Wolfgang Denk
2010-09-08 21:00               ` Scott Wood
2010-09-09  7:26                 ` Wolfgang Denk
2010-09-09 16:28                   ` Scott Wood
2010-09-09 17:22                     ` Wolfgang Denk [this message]
2010-09-09 14:07               ` Lei Wen
2010-09-08 23:27       ` Loïc Minier
2010-09-09  8:57         ` Wolfgang Denk
2010-09-12 15:07           ` Loïc Minier
2010-09-12 17:37             ` Wolfgang Denk
2010-09-13  4:20               ` Nicolas Pitre
2010-09-13  9:17                 ` Wolfgang Denk
2010-09-13 13:37                   ` Nicolas Pitre
2010-09-13 21:59                     ` Wolfgang Denk
2010-09-14  3:23                       ` Nicolas Pitre

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=20100909172221.37AB41506AA@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