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:39:05 +0100	[thread overview]
Message-ID: <476BDE19.50409@semihalf.com> (raw)
In-Reply-To: <20071221151740.2317A248AC@gemini.denx.de>

Wolfgang Denk wrote:
> In message <476BD5E9.3030601@semihalf.com> you wrote:
>>> 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
> 
> It certainly makes sense to factor out this code, but I'm not sure yet
> if a separate command will be needed.
> 
>> execution from bootm to a dedicated hook that'll be available from
>> 'imrun'. This way, bootm would become strict OS booting command,
> 
> But "bootm" already *is* a strict OS booting command.
> 
> I'm not sure what  youre  reference  to  standalone  applications  is
> supposed  to  mean  in  this contexzt - but SA apps are NOT booted by
> bootm, they get started using the "go" command.

What I meant was that bootm accepts also uImages of type
IH_TYPE_STANDALONE, which corresponds to standalone applications. If
such uImage is passed to bootm and autostart is not set to 'no', bootm
will execute it. That kind of image processing would perfectly fit
hooks framework.

Cheers,
Marian

      reply	other threads:[~2007-12-21 15:39 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
2007-12-21 15:17         ` Wolfgang Denk
2007-12-21 15:39           ` Marian Balakowicz [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=476BDE19.50409@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