From: Sascha Hauer <s.hauer@pengutronix.de>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Lior Amsalem <alior@marvell.com>,
barebox@lists.infradead.org, Willy Tarreau <w@1wt.eu>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Subject: Re: [PATCH v3 0/7] Basic support for Armada 370/XP SOCs
Date: Sun, 12 May 2013 12:24:04 +0200 [thread overview]
Message-ID: <20130512102404.GV32299@pengutronix.de> (raw)
In-Reply-To: <20130512111246.72df8918@skate>
On Sun, May 12, 2013 at 11:12:46AM +0200, Thomas Petazzoni wrote:
> Dear Sascha Hauer,
>
> On Sun, 12 May 2013 09:56:44 +0200, Sascha Hauer wrote:
> > There is a problem with this series: It doesn't build without the
> > addtional binary needed for the kwb tool. Can we make creating a kwb
> > image optional so that we are able to build the defconfigs without
> > additional dependencies?
>
> Hum, right. So we should make the default build target to not build
> barebox.{kwb,kwbuart} and only make barebox.bin?
>
> Or there should be a config option somewhere to say "I also want
> the .{kwb,kwbuart} images generated" ?
>
> Neither of those are ideal, because most likely people will not notice
> the possibility of building the .{kwb,kwbuart} images, but I understand
> the concern of not being able to build defconfigs.
>
> Tell me which solution you prefer, and I'll send a patch that
> implements it.
How about a warning like:
"Warning: 'plathome-openblocks-ax3-binary.0' does not exist. Not building barebox.kwb"
Also not an ideal solution, but I think there is no really good way to
solve this other than including the binary in the tree which probably
has some licensing issues.
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-05-12 10:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 9:52 Thomas Petazzoni
2013-05-09 9:52 ` [PATCH v3 1/7] scripts: new kwbimage manipulation tool for Marvell SoC boot images Thomas Petazzoni
2013-05-09 9:52 ` [PATCH v3 2/7] scripts: add kwboot tool Thomas Petazzoni
2013-05-09 11:16 ` Jason Cooper
2013-05-10 13:25 ` Sascha Hauer
2013-05-09 9:52 ` [PATCH v3 3/7] arm: initial support for Marvell Armada 370/XP SoCs Thomas Petazzoni
2013-05-12 11:14 ` antonynpavlov
2013-05-09 9:52 ` [PATCH v3 4/7] arm: integrate kwbimage in the image generation Thomas Petazzoni
2013-05-09 9:52 ` [PATCH v3 5/7] arm: add basic support for Armada XP OpenBlocks AX3 platform Thomas Petazzoni
2013-05-09 9:52 ` [PATCH v3 6/7] arm: add basic support for the Armada 370 Mirabox platform Thomas Petazzoni
2013-05-09 9:52 ` [PATCH v3 7/7] arm: add basic support for the Armada XP GP platform Thomas Petazzoni
2013-05-09 13:33 ` [PATCH v3 0/7] Basic support for Armada 370/XP SOCs Gregory CLEMENT
2013-05-11 15:27 ` Sascha Hauer
2013-05-11 16:27 ` Thomas Petazzoni
2013-05-12 7:56 ` Sascha Hauer
2013-05-12 9:12 ` Thomas Petazzoni
2013-05-12 10:24 ` Sascha Hauer [this message]
2013-05-12 10:41 ` Thomas Petazzoni
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=20130512102404.GV32299@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alior@marvell.com \
--cc=barebox@lists.infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=w@1wt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox