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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox