From: Sascha Hauer <s.hauer@pengutronix.de>
To: Christian Kapeller <christian.kapeller@cmotion.eu>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] arm: support booting of uimages with as barebox payload.
Date: Tue, 17 Jul 2012 17:34:44 +0200 [thread overview]
Message-ID: <20120717153444.GA30009@pengutronix.de> (raw)
In-Reply-To: <5005674F.9030706@cmotion.eu>
On Tue, Jul 17, 2012 at 03:23:27PM +0200, Christian Kapeller wrote:
> On 07/17/2012 02:49 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 13:23 Tue 17 Jul , Christian Kapeller wrote:
> >> Packing barebox within an uimage gives us integrity checking.
> >>
> >> Generate the image with:
> >> ./scripts/mkimage -A arm -O barebox -T firmware -C none -d barebox.bin -a 0xffffffff barebox.uimage
> >>
> >> Signed-off-by: Christian Kapeller <christian.kapeller@cmotion.eu>
> >> ---
> > boot it as a linux kernel
> >
> > it will work
>
> You are right, it does. But then, I am asking myself, why is there a OS
> definition for 'barebox', when we aren't using it in the first place?
It's derived from U-Boot where it initially was:
#define IH_OS_U_BOOT 17 /* Firmware */
When renaming U-Boot to barebox this was one of the occurences of
'U_BOOT' that shouldn't have been renamed.
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
prev parent reply other threads:[~2012-07-17 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 11:23 [PATCH] arm: support booting of uimages with as barebox payload Christian Kapeller
2012-07-17 12:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-07-17 13:23 ` Christian Kapeller
2012-07-17 15:34 ` Sascha Hauer [this message]
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=20120717153444.GA30009@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=christian.kapeller@cmotion.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.