From: Sascha Hauer <s.hauer@pengutronix.de>
To: Trent Piepho <tpiepho@kymetacorp.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] Make barebox flashable image link for "multi-image" targets
Date: Wed, 21 Oct 2015 08:01:23 +0200 [thread overview]
Message-ID: <20151021060123.GW14476@pengutronix.de> (raw)
In-Reply-To: <1445377655.13196.99.camel@rtred1test09.kymetacorp.com>
On Tue, Oct 20, 2015 at 09:47:30PM +0000, Trent Piepho wrote:
> For a target with multi-image support, no barebox-flash-image link is
> made pointing to the finished flashable image. This makes it hard for
> buildroot to figure out which file is the barebox image. And one has
> to assume this link is generally useful and convenient to users of
> barebox, or why would it have been created in the first place?
Creating the barebox-flash-image link predates the multiimage support,
so by the time it was introduced it was not clear to me that there will
be no single image later anymore.
>
> This patch to the multi-image build will create that link.
>
> It only works when a single image is made. If one is making multiple
> images, then the concept of a single finished image no longer applies,
> and no link is made.
Can't you make the image a config option in buildroot? Depending on only
having a single image selected in barebox doesn't sound like a good
idea.
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:[~2015-10-21 6:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 21:47 Trent Piepho
2015-10-21 6:01 ` Sascha Hauer [this message]
2015-10-21 18:09 ` Trent Piepho
2015-10-22 7:06 ` Sascha Hauer
2015-10-22 18:48 ` Trent Piepho
2015-10-26 6:22 ` 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=20151021060123.GW14476@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=tpiepho@kymetacorp.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