From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751350AbcCACsL (ORCPT <rfc822;w@1wt.eu>);
	Mon, 29 Feb 2016 21:48:11 -0500
Received: from mga14.intel.com ([192.55.52.115]:32974 "EHLO mga14.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750888AbcCACsK (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 29 Feb 2016 21:48:10 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.22,521,1449561600"; 
   d="scan'208";a="661539016"
Date: Tue, 1 Mar 2016 10:48:05 +0800
From: Fengguang Wu <fengguang.wu@intel.com>
To: 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
Message-ID: <20160301024805.GA22727@wfg-t540p.sh.intel.com>
References: <201602280726.PTUabuDo%fengguang.wu@intel.com>
 <CAMuHMdW-5j39TTZv0j2vKRk9N+D2ya9GTEJy4N4etjq-B2kYZw@mail.gmail.com>
 <20160301020619.GA18677@wfg-t540p.sh.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160301020619.GA18677@wfg-t540p.sh.intel.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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>

I do see there is an xtensa patch 2 years ago:

http://lists.denx.de/pipermail/u-boot/2014-April/178467.html

Thanks,
Fengguang