From: Michael Ellerman <mpe@ellerman.id.au>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] common: image: Allow mkimage to build a uImage for extensa
Date: Wed, 30 Apr 2014 11:57:59 +1000 [thread overview]
Message-ID: <1398823079.5722.3.camel@concordia> (raw)
In-Reply-To: <CAOMZO5CGeBCB6G2GP=QMTssCKhHuk9BdQ82bMBK7Ka5+Q7j4FQ@mail.gmail.com>
On Tue, 2014-04-29 at 12:52 -0300, Fabio Estevam wrote:
> On Tue, Apr 29, 2014 at 12:48 PM, Wolfgang Denk <wd@denx.de> wrote:
> > Dear Fabio,
> >
> > In message <CAOMZO5BozLxi65cknttwu2hA0OGy_N=VZBbwm7_WWMaRBbKK6w@mail.gmail.com> you wrote:
> >>
> >> Looks like the quick fix is for Michael/Geert do not build uImage for
> >> xtensa on their automated build environments.
> >
> > What would you do with an uImage file when there is no U-Boot to load
> > it?
>
> Michael's build system builds uImage for xtensa:
> http://kisskb.ellerman.id.au/kisskb/buildresult/10665903/
>
> so it makes more sense simply not to build uImage for such architecture.
It just runs "make".
The decision about building a uImage must be in the .config somewhere.
This failure is for allnoconfig, so presumably there is something like a
CONFIG_DONT_BUILD_UIMAGE which is getting set to n by allnoconfig. If you can
tell me what that option is I can force it back on (I think).
cheers
next prev parent reply other threads:[~2014-04-30 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 4:48 [U-Boot] [PATCH] common: image: Allow mkimage to build a uImage for extensa Fabio Estevam
2014-04-29 4:55 ` czankel
2014-04-29 10:24 ` Wolfgang Denk
2014-04-29 15:04 ` Fabio Estevam
2014-04-29 15:48 ` Wolfgang Denk
2014-04-29 15:52 ` Fabio Estevam
2014-04-30 1:57 ` Michael Ellerman [this message]
2014-04-30 18:05 ` Fabio Estevam
2014-04-29 17:11 ` Chris Zankel
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=1398823079.5722.3.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=u-boot@lists.denx.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