From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marian Balakowicz Date: Fri, 21 Dec 2007 16:39:05 +0100 Subject: [U-Boot-Users] RFC: New U-boot image format In-Reply-To: <20071221151740.2317A248AC@gemini.denx.de> References: <20071221151740.2317A248AC@gemini.denx.de> Message-ID: <476BDE19.50409@semihalf.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.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