From: Michael Ellerman <mpe@ellerman.id.au>
To: Fabio Estevam <festevam@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next <linux-next@vger.kernel.org>
Subject: Re: kissb mkimage doesn't support extensa
Date: Tue, 29 Apr 2014 17:50:54 +1000 [thread overview]
Message-ID: <1398757854.27852.0.camel@concordia> (raw)
In-Reply-To: <CAOMZO5ADi5=pUYfknESjJfYXBn_xwQJ0zyG5=tRmzDpZoaf8Sw@mail.gmail.com>
On Tue, 2014-04-29 at 01:42 -0300, Fabio Estevam wrote:
> On Tue, Apr 29, 2014 at 12:50 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> > On Sun, 2014-03-02 at 11:25 +0100, Geert Uytterhoeven wrote:
> >> http://kisskb.ellerman.id.au/kisskb/buildresult/10665903/
> >>
> >> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k,
> >> microblaze, mips, mips64, nios, nios2, ppc, s390, sh, sparc, sparc64,
> >> blackfin, avr32
> >
> > I've upgraded to the latest version in Debian (2014.01), but it still doesn't
> > seem to support xtensa.
> >
> > $ /usr/bin/mkimage -A xtensa
> >
> > Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze,
> > mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32,
> > nds32, or1k, sandbox, arm64
>
> I will submit a patch to U-boot in order to include extensa and will
> Cc you and Geert.
Thanks.
cheers
next prev parent reply other threads:[~2014-04-29 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 10:25 kissb mkimage doesn't support extensa Geert Uytterhoeven
2014-04-29 3:50 ` Michael Ellerman
2014-04-29 4:42 ` Fabio Estevam
2014-04-29 7:50 ` Michael Ellerman [this message]
2014-04-30 18:31 ` Fabio Estevam
2014-04-30 19:34 ` Max Filippov
2014-04-30 20:53 ` Geert Uytterhoeven
2014-05-01 0:45 ` Max Filippov
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=1398757854.27852.0.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=festevam@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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