From: Michael Ellerman <mpe@ellerman.id.au>
To: Fengguang Wu <fengguang.wu@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-all] 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
Date: Tue, 01 Mar 2016 14:15:27 +1100 [thread overview]
Message-ID: <1456802127.21548.6.camel@ellerman.id.au> (raw)
In-Reply-To: <20160301024805.GA22727@wfg-t540p.sh.intel.com>
On Tue, 2016-03-01 at 10:48 +0800, Fengguang Wu wrote:
> On Tue, Mar 01, 2016 at 10:06:19AM +0800, Fengguang Wu wrote:
> > Hi Geert,
> >
> > > > make.cross ARCH=xtensa
> > > >
> > > > All errors (new ones prefixed by >>):
> > > >
> > > > > > 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
> > > > Usage: /usr/bin/mkimage -l image
> > >
> > > Don't you just need to update mkimage to a version that does have
> > > xtensa support?
> >
> > Yeah, thanks for the suggestion!
> > I'll upgrade the u-boot-tools package which contains /usr/bin/mkimage.
>
> Hi Geert,
>
> I've upgraded the Debian u-boot-tools to 2016.01+dfsg1-2:
>
> Desired=Unknown/Install/Remove/Purge/Hold
> > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> > / Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> > > / Name Version Architecture Description
> +++-====================================-=======================-=======================-=============================================================================
> ii u-boot-tools 2016.01+dfsg1-2 amd64 companion tools for Das U-Boot bootloader
>
> But still find it not support xtensa..
>
> $ strings /usr/bin/mkimage|g xtensa
> <EMPTY>
Hmm, true, same here.
Kisskb is building xtensa happily, there must be something in .config which
controls whether it uses mkimage?
http://kisskb.ellerman.id.au/kisskb/buildresult/12621125/
http://kisskb.ellerman.id.au/kisskb/target/2029/
cheers
next prev parent reply other threads:[~2016-03-01 3:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 23:51 kbuild test robot
2016-02-28 8:43 ` Geert Uytterhoeven
2016-03-01 2:06 ` [kbuild-all] " Fengguang Wu
2016-03-01 2:48 ` Fengguang Wu
2016-03-01 3:15 ` Michael Ellerman [this message]
2016-03-01 3:30 ` Fengguang Wu
2016-02-28 9:24 ` Thomas Gleixner
2016-03-01 2:26 ` [kbuild-all] " Fengguang Wu
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=1456802127.21548.6.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=fengguang.wu@intel.com \
--cc=geert@linux-m68k.org \
--cc=john.stultz@linaro.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®