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
