Re: [PATCH] arm: add support to generate uImage

From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] arm: add support to generate uImage
Date: Mon, 25 Apr 2011 20:57:04 +0200	[thread overview]
Message-ID: <20110425185704.GG14770@pengutronix.de> (raw)
In-Reply-To: <20110425154834.GC13557@game.jcrosoft.org>

On Mon, Apr 25, 2011 at 05:48:34PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > +	hex
> > > +	default TEXT_BASE
> > > +	help
> > > +	  The Address barebox gets load at as a uImage
> > > +
> > 
> > No, please don't. When you load barebox with itself you end up
> > overwriting the running barebox with the just loaded image if using
> > TEXT_BASE here.
> > barebox can be started from any address in SDRAM. Isn't there a
> > mechanism to support this with the uImage format? The U-Boot guys have
> > the same problem with ARM_PATCH_PHYS_VIRT in the kernel aswell, so I
> > assume this is already solved in some way, no?
> I known but the uImage does not allow you to do so
> and no they do not do so
> 
> for us we can add a -l and -e option to bootm to overwrite the default load address
> and entry point but for orlder u-boot or barebox we can not so this is the
> only way to specify one for the uImage

Then the sdram base address is a much safer default value. We also
should add a check in the uImage code that prevents us from overwriting
ourselves.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox