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-Users] RFC: New U-boot image format
Date: Thu, 20 Dec 2007 20:42:58 +0100	[thread overview]
Message-ID: <20071220194258.D5A37248ED@gemini.denx.de> (raw)
In-Reply-To: Your message of "Wed, 19 Dec 2007 15:07:09 +0100." <4769258D.6090709@semihalf.com>

In message <4769258D.6090709@semihalf.com> you wrote:
>
> The hooks idea sounds reasonable but, the problem
> is that there isn't really any such thing like
> "main fromat processing code".
> 
> The 'bootm' command code does a lot of image
> related manipulation but it's not generic or main
> format processing code. It is rather a specialized

But it's *the* generic command for booting a Linux kernel.

> command that handles one thing, starting
> executables, like kernels or standalone
> applications. And it's a command, it will not do
> anything unless directly called.

Correct.

> So, having hooks in bootm, you would need to call
> bootm and then your 'qe fw' command which is sort
> of wired.

MY current understandign is, that when  running  "bootm",  the  bootm
command  would detect if there are registred hook routines for any of
the contained sub-images, and run that code automagically.

> There are also other commands that deal with the
> images, these are other boot commands like
> scsiboot, usbboot, etc, and also imls, imxtract.

scsiboot, usbboot etc. are just means to load an image into RAM,
similar to tftpboot or dhcpboot. If they also boot the loaded image
(because autostart is set to yes), then they do so by calling bootm
internally. So everything is fine.

imls would probably have it's ownset of image type hooks - while  you
would  register some "boot me" type of handlers with bootm, you would
register some "display me" type of handlers with imls.

imxtract will have to be changed completely in any case.

> And all of them process images directly, finding
> necessary information on their own.

This is no argument for not  creating  some  more  centralized  image
processing code, or is it?

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
By the way, ALL software projects are done by iterative  prototyping.
Some companies call their prototypes "releases", that's all.

  reply	other threads:[~2007-12-20 19:42 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
2007-12-18 20:18             ` Timur Tabi
2007-12-19 14:07   ` Marian Balakowicz
2007-12-20 19:42     ` Wolfgang Denk [this message]
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=20071220194258.D5A37248ED@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