Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1346293

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

From Fengguang Wu <fengguang.wu@intel.com>
Newsgroups linux.kernel
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 2016-03-01 03:10 +0100
Message-ID <r7HV8-2Mh-3@gated-at.bofh.it> (permalink)
References <r6WMx-1YM-1@gated-at.bofh.it> <r75d8-89y-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

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.

Thanks,
Fengguang

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

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 kbuild test robot <fengguang.wu@intel.com> - 2016-02-28 00:50 +0100
  Re: 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 Geert Uytterhoeven <geert@linux-m68k.org> - 2016-02-28 09:50 +0100
    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 Fengguang Wu <fengguang.wu@intel.com> - 2016-03-01 03:10 +0100
      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 Fengguang Wu <fengguang.wu@intel.com> - 2016-03-01 03:50 +0100
        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 Michael Ellerman <mpe@ellerman.id.au> - 2016-03-01 04:20 +0100
          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 Fengguang Wu <fengguang.wu@intel.com> - 2016-03-01 04:40 +0100
  Re: 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 Thomas Gleixner <tglx@linutronix.de> - 2016-02-28 10:30 +0100
    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 Fengguang Wu <fengguang.wu@intel.com> - 2016-03-01 03:30 +0100

csiph-web