From: Sascha Hauer <s.hauer@pengutronix.de>
To: Teresa Gamez <t.gamez@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: AM335x MLO images broken
Date: Wed, 9 Jul 2014 18:47:07 +0200 [thread overview]
Message-ID: <20140709164707.GC23235@pengutronix.de> (raw)
In-Reply-To: <1404921012.3612.15.camel@lws-gamez.phytec.de>
On Wed, Jul 09, 2014 at 05:50:12PM +0200, Teresa Gamez wrote:
> Hello Sascha,
>
> since
>
> commit d1ec6fb0c9bb66939e85964c2f5214b117c78ecf
> Author: Sascha Hauer <s.hauer@pengutronix.de>
> Date: Mon Jul 7 14:13:14 2014 +0200
>
> ARM: OMAP: Do not show MLO/SPI image options with OMAP_MULTI_BOARDS
>
>
> the creation of a proper MLO image is not working any more. When I run
> make am335x_mlo_defconfig && make I get:
> ..
> images built:
> barebox-am33xx-phytec-phycore.img
> barebox-am33xx-beaglebone.img
>
> instead of the expected
>
> barebox-am33xx-phytec-phycore-mlo.img
> barebox-am33xx-beaglebone-mlo.img
>
> and they also won't work.
Looks like a side effect of:
| commit d1ec6fb0c9bb66939e85964c2f5214b117c78ecf
| Author: Sascha Hauer <s.hauer@pengutronix.de>
| Date: Mon Jul 7 14:13:14 2014 +0200
|
| ARM: OMAP: Do not show MLO/SPI image options with OMAP_MULTI_BOARDS
|
| The MLO/SPI image options have no effect with OMAP_MULTI_BOARDS
| enabled, so do not show them.
|
| Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
I haven't looked whether there's a better solution than reverting the
commit.
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:[~2014-07-09 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 15:50 Teresa Gamez
2014-07-09 16:47 ` Sascha Hauer [this message]
2014-07-10 7:37 Rolf Evers-Fischer
2014-07-10 21:28 ` 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=20140709164707.GC23235@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=t.gamez@phytec.de \
/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