From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] bootm: add u-boot support
Date: Wed, 18 Sep 2013 09:03:42 +0200 [thread overview]
Message-ID: <20130918070342.GL30088@pengutronix.de> (raw)
In-Reply-To: <1379404339-6716-2-git-send-email-plagnioj@jcrosoft.com>
On Tue, Sep 17, 2013 at 09:52:19AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> Simply do the same as barebox and hope for the best as u-boot does not handle
> runtime address detection for boot quite often. It does only execpt you to
> choose as compiling time.
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> ---
> arch/arm/lib/bootm.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm/lib/bootm.c b/arch/arm/lib/bootm.c
> index 599b09a..71200be 100644
> --- a/arch/arm/lib/bootm.c
> +++ b/arch/arm/lib/bootm.c
> @@ -315,6 +315,12 @@ static struct image_handler barebox_handler = {
> .filetype = filetype_arm_barebox,
> };
>
> +static struct image_handler uboot_handler = {
> + .name = "ARM u-boot",
> + .bootm = do_bootm_barebox,
> + .filetype = filetype_arm_uboot,
> +};
> +
Wolfgang always emphasizes that it's not possible to start U-Boot second
stage. Most U-Boot images indeed do not support this without hacking the
lowlevel code. We can't support this feature which happens to work on
only some U-Boot images.
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
next prev parent reply other threads:[~2013-09-18 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 7:52 [PATCH 1/2] filetype: add arm " Jean-Christophe PLAGNIOL-VILLARD
2013-09-17 7:52 ` [PATCH 2/2] bootm: add " Jean-Christophe PLAGNIOL-VILLARD
2013-09-18 7:03 ` Sascha Hauer [this message]
2013-09-19 11:50 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-18 7:00 ` [PATCH 1/2] filetype: add arm " Sascha Hauer
2013-09-19 11:56 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-20 6:29 ` Sascha Hauer
2013-09-20 8:02 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-20 11:56 ` Sascha Hauer
2013-09-21 6:53 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-21 8:10 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130918070342.GL30088@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox