From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
Date: Fri, 16 Sep 2005 15:07:14 +0200
Subject: [U-Boot-Users] bootm and script images
In-Reply-To: <20050916105100.0F3F1352B7B@atlas.denx.de>
References: <20050916105100.0F3F1352B7B@atlas.denx.de>
Message-ID: <432AC382.1050903@esd-electronics.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Wolfgang,

this is what I need to do: we have u-boot running on a PCI adapter card.
The whatever-image is directly loaded into the card's RAM over the PCI 
bus. Then we trigger booting the image by modifying a magic RAM cell.

Currently only Linux kernel images and combined kernel + initrd images 
are supported. Now we want to allow using u-boot scripts with the same 
mechanism.

So if you think that a "universal" boot command would blow things up to 
much, I will think of a mofication of our loadpci BSP command. I will 
decide inside this command if bootm or autoscr must be used.

Wolfgang Denk wrote:
> Yes. Bootm is intended to boot (Linux)  kernel  images,  that's  all.
> There  are  other  commands to deal with other objects, like "go" for
> standalone images, "autoscr" for scripts,
Yes, I know.
> 
> Please keep the design smalland simple. We don't need no  eierlegende
> Woll-Milch-S?ue in U-Boot :-)
Well, it would be just one more case in the bootm switch statement.

Matthias