public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marian Balakowicz <m8@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: New U-boot image format
Date: Fri, 21 Dec 2007 16:04:09 +0100	[thread overview]
Message-ID: <476BD5E9.3030601@semihalf.com> (raw)
In-Reply-To: <20071220194258.D5A37248ED@gemini.denx.de>

Wolfgang Denk wrote:
> 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.

Right.

[...]
> 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?

No, it's not. But I have doubts whether bootm is a good place for it.
Maybe we should rather go for new generic command, something like
'imrun' or similar. And maybe even, move standalone application
execution from bootm to a dedicated hook that'll be available from
'imrun'. This way, bootm would become strict OS booting command,
potentially also available from 'imrun' via a hook.

How that sounds?

Cheers,
Marian

  reply	other threads:[~2007-12-21 15:04 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
2007-12-21 15:04       ` Marian Balakowicz [this message]
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=476BD5E9.3030601@semihalf.com \
    --to=m8@semihalf.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