On Tue, Apr 29, 2014 at 12:50 AM, Michael Ellerman <mpe@xxxxxxxxxxxxxx> 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 As mainline U-boot does not support xtensa currently, what about dropping the uImage format to be built? --- a/arch/xtensa/boot/Makefile +++ b/arch/xtensa/boot/Makefile @@ -22,8 +22,8 @@ subdir-y := lib # Subdirs for the boot loader(s) bootdir-$(CONFIG_XTENSA_PLATFORM_ISS) += boot-elf -bootdir-$(CONFIG_XTENSA_PLATFORM_XT2000) += boot-redboot boot-elf boot-uboot -bootdir-$(CONFIG_XTENSA_PLATFORM_XTFPGA) += boot-redboot boot-elf boot-uboot +bootdir-$(CONFIG_XTENSA_PLATFORM_XT2000) += boot-redboot boot-elf +bootdir-$(CONFIG_XTENSA_PLATFORM_XTFPGA) += boot-redboot boot-elf zImage Image: $(bootdir-y) @@ -41,4 +41,3 @@ vmlinux.bin.gz: vmlinux.bin FORCE boot-elf: vmlinux.bin boot-redboot: vmlinux.bin.gz -boot-uboot: vmlinux.bin.gz -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
