linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* kissb mkimage doesn't support extensa
@ 2014-03-02 10:25 Geert Uytterhoeven
  2014-04-29  3:50 ` Michael Ellerman
  0 siblings, 1 reply; 8+ messages in thread
From: Geert Uytterhoeven @ 2014-03-02 10:25 UTC (permalink / raw)
  To: Stephen Rothwell, Michael Ellerman; +Cc: Linux-Next

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
Usage: /usr/local/bin/mkimage -l image
          -l ==> list image header information
       /usr/local/bin/mkimage [-x] -A arch -O os -T type -C comp -a
addr -e ep -n name -d data_file[:data_file...] image
          -A ==> set architecture to 'arch'
          -O ==> set operating system to 'os'
          -T ==> set image type to 'type'
          -C ==> set compression type 'comp'
          -a ==> set load address to 'addr' (hex)
          -e ==> set entry point to 'ep' (hex)
          -n ==> set image name to 'name'
          -d ==> use image data from 'datafile'
          -x ==> set XIP (execute in place)
make[3]: *** [arch/xtensa/boot/boot-uboot/../uImage] Error 1

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kissb mkimage doesn't support extensa
  2014-03-02 10:25 kissb mkimage doesn't support extensa Geert Uytterhoeven
@ 2014-04-29  3:50 ` Michael Ellerman
  2014-04-29  4:42   ` Fabio Estevam
  2014-04-30 18:31   ` Fabio Estevam
  0 siblings, 2 replies; 8+ messages in thread
From: Michael Ellerman @ 2014-04-29  3:50 UTC (permalink / raw)
  To: Geert Uytterhoeven; +Cc: Stephen Rothwell, Linux-Next

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

cheers

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kissb mkimage doesn't support extensa
  2014-04-29  3:50 ` Michael Ellerman
@ 2014-04-29  4:42   ` Fabio Estevam
  2014-04-29  7:50     ` Michael Ellerman
  2014-04-30 18:31   ` Fabio Estevam
  1 sibling, 1 reply; 8+ messages in thread
From: Fabio Estevam @ 2014-04-29  4:42 UTC (permalink / raw)
  To: Michael Ellerman; +Cc: Geert Uytterhoeven, Stephen Rothwell, Linux-Next

On Tue, Apr 29, 2014 at 12:50 AM, Michael Ellerman <mpe@ellerman.id.au> 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

I will submit a patch to U-boot in order to include extensa and will
Cc you and Geert.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kissb mkimage doesn't support extensa
  2014-04-29  4:42   ` Fabio Estevam
@ 2014-04-29  7:50     ` Michael Ellerman
  0 siblings, 0 replies; 8+ messages in thread
From: Michael Ellerman @ 2014-04-29  7:50 UTC (permalink / raw)
  To: Fabio Estevam; +Cc: Geert Uytterhoeven, Stephen Rothwell, Linux-Next

On Tue, 2014-04-29 at 01:42 -0300, Fabio Estevam wrote:
> On Tue, Apr 29, 2014 at 12:50 AM, Michael Ellerman <mpe@ellerman.id.au> 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
> 
> I will submit a patch to U-boot in order to include extensa and will
> Cc you and Geert.

Thanks.

cheers

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kissb mkimage doesn't support extensa
  2014-04-29  3:50 ` Michael Ellerman
  2014-04-29  4:42   ` Fabio Estevam
@ 2014-04-30 18:31   ` Fabio Estevam
  2014-04-30 19:34     ` Max Filippov
  1 sibling, 1 reply; 8+ messages in thread
From: Fabio Estevam @ 2014-04-30 18:31 UTC (permalink / raw)
  To: Michael Ellerman; +Cc: Geert Uytterhoeven, Stephen Rothwell, Linux-Next

On Tue, Apr 29, 2014 at 12:50 AM, Michael Ellerman <mpe@ellerman.id.au> 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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kissb mkimage doesn't support extensa
  2014-04-30 18:31   ` Fabio Estevam
@ 2014-04-30 19:34     ` Max Filippov
  2014-04-30 20:53       ` Geert Uytterhoeven
  0 siblings, 1 reply; 8+ messages in thread
From: Max Filippov @ 2014-04-30 19:34 UTC (permalink / raw)
  To: Fabio Estevam
  Cc: Michael Ellerman, Geert Uytterhoeven, Stephen Rothwell, Linux-Next

On Wed, Apr 30, 2014 at 10:31 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Tue, Apr 29, 2014 at 12:50 AM, Michael Ellerman <mpe@ellerman.id.au> 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?

There's xtensa port for U-boot at https://github.com/foss-xtensa/u-boot
Also KISSKB didn't even try to build uImage for xtensa until recently.
What's changed?

-- 
Thanks.
-- Max

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kissb mkimage doesn't support extensa
  2014-04-30 19:34     ` Max Filippov
@ 2014-04-30 20:53       ` Geert Uytterhoeven
  2014-05-01  0:45         ` Max Filippov
  0 siblings, 1 reply; 8+ messages in thread
From: Geert Uytterhoeven @ 2014-04-30 20:53 UTC (permalink / raw)
  To: Max Filippov
  Cc: Fabio Estevam, Michael Ellerman, Stephen Rothwell, Linux-Next,
	linux-kbuild

On Wed, Apr 30, 2014 at 9:34 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
> On Wed, Apr 30, 2014 at 10:31 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Tue, Apr 29, 2014 at 12:50 AM, Michael Ellerman <mpe@ellerman.id.au> 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?
>
> There's xtensa port for U-boot at https://github.com/foss-xtensa/u-boot
> Also KISSKB didn't even try to build uImage for xtensa until recently.
> What's changed?

When comparing the build between 18a1a7a1 (good) and a7963eb7f4
(bad), it seems allnoconfig changes the build type from ISS to XT2000.
The latter builds boot-uboot, too, cfr. arch/xtensa/boot/Makefile.

So I guess it's due to this change to kconfig:

commit 5d2acfc7b974bbd3858b4dd3f2cdc6362dd8843a
Author: Josh Triplett <josh@joshtriplett.org>
Date:   Mon Apr 7 15:39:09 2014 -0700

    kconfig: make allnoconfig disable options behind EMBEDDED and EXPERT

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kissb mkimage doesn't support extensa
  2014-04-30 20:53       ` Geert Uytterhoeven
@ 2014-05-01  0:45         ` Max Filippov
  0 siblings, 0 replies; 8+ messages in thread
From: Max Filippov @ 2014-05-01  0:45 UTC (permalink / raw)
  To: Geert Uytterhoeven
  Cc: Fabio Estevam, Michael Ellerman, Stephen Rothwell, Linux-Next,
	linux-kbuild

On Thu, May 1, 2014 at 12:53 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Wed, Apr 30, 2014 at 9:34 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
>> On Wed, Apr 30, 2014 at 10:31 PM, Fabio Estevam <festevam@gmail.com> wrote:
>>> On Tue, Apr 29, 2014 at 12:50 AM, Michael Ellerman <mpe@ellerman.id.au> 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?
>>
>> There's xtensa port for U-boot at https://github.com/foss-xtensa/u-boot
>> Also KISSKB didn't even try to build uImage for xtensa until recently.
>> What's changed?
>
> When comparing the build between 18a1a7a1 (good) and a7963eb7f4
> (bad), it seems allnoconfig changes the build type from ISS to XT2000.

Ok, then we'd better restore ISS as the default platform for allnoconfig:

diff --git a/arch/xtensa/Kconfig b/arch/xtensa/Kconfig
index 17b3198..2ca8819 100644
--- a/arch/xtensa/Kconfig
+++ b/arch/xtensa/Kconfig
@@ -243,7 +243,6 @@ choice

 config XTENSA_PLATFORM_ISS
        bool "ISS"
-       depends on TTY
        select XTENSA_CALIBRATE_CCOUNT
        select SERIAL_CONSOLE
        help
diff --git a/arch/xtensa/platforms/iss/Makefile
b/arch/xtensa/platforms/iss/Makefile
index d2369b7..b3e8929 100644
--- a/arch/xtensa/platforms/iss/Makefile
+++ b/arch/xtensa/platforms/iss/Makefile
@@ -4,6 +4,7 @@
 # "prom monitor" library routines under Linux.
 #

-obj-y                  = console.o setup.o
+obj-y                  = setup.o
+obj-$(CONFIG_TTY)      += console.o
 obj-$(CONFIG_NET)      += network.o
 obj-$(CONFIG_BLK_DEV_SIMDISK) += simdisk.o

-- 
Thanks.
-- Max

^ permalink raw reply related	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2014-05-01  0:45 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-03-02 10:25 kissb mkimage doesn't support extensa Geert Uytterhoeven
2014-04-29  3:50 ` Michael Ellerman
2014-04-29  4:42   ` Fabio Estevam
2014-04-29  7:50     ` Michael Ellerman
2014-04-30 18:31   ` Fabio Estevam
2014-04-30 19:34     ` Max Filippov
2014-04-30 20:53       ` Geert Uytterhoeven
2014-05-01  0:45         ` Max Filippov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).