[PATCH v2] bootm: update os_entry from uimage
Sascha Hauer
s.hauer at pengutronix.de
Mon Sep 23 05:13:09 EDT 2013
On Mon, Sep 23, 2013 at 10:16:00AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 17:20 Sat 21 Sep , Jean-Christophe PLAGNIOL-VILLARD wrote:
> > if not uimage set 0 by default
> >
> > today we do not see the issue as the kernel entry point is the same as the
> > load_addr but on other binary its not necessary the case
> >
> > as today we ignore the entry point set in the uimage and just assume it's the
> > same as the load_addr
> >
> > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj at jcrosoft.com>
> > ---
>
> this patch will also prepare to add a globalval and a getopt to overwrite the
> os_entry
We already have a getopt to overwrite the os_entry: -e
>
> yours do not care about this preparation by not setting
> data.os_entry = UIMAGE_SOME_ADDRESS;
Because UIMAGE_SOME_ADDRESS is not suitable for a relative offset to the
image start.
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 |
More information about the barebox
mailing list