On Tue, Apr 29, 2014 at 10:57 PM, Michael Ellerman wrote:
> It just runs "make".
>
> The decision about building a uImage must be in the .config somewhere.
>
> This failure is for allnoconfig, so presumably there is something like a
> CONFIG_DONT_BUILD_UIMAGE which is getting set to n by allnocon
On Tue, 2014-04-29 at 12:52 -0300, Fabio Estevam wrote:
> On Tue, Apr 29, 2014 at 12:48 PM, Wolfgang Denk wrote:
> > Dear Fabio,
> >
> > In message
> > you
> > wrote:
> >>
> >> Looks like the quick fix is for Michael/Geert do not build uImage for
> >> xtensa on their automated build environment
Hi,
I have a port for the Xtensa architecture ready, and it would be great
if you could include it in the mainline tree. I still have to finish
another project, but could start sending patches for RFC to this mailing
list in a week or two.
Thanks,
-Chris
On 4/29/14, 8:48 AM, Wolfgang Denk w
On Tue, Apr 29, 2014 at 12:48 PM, Wolfgang Denk wrote:
> Dear Fabio,
>
> In message
> you
> wrote:
>>
>> Looks like the quick fix is for Michael/Geert do not build uImage for
>> xtensa on their automated build environments.
>
> What would you do with an uImage file when there is no U-Boot to lo
Dear Fabio,
In message
you wrote:
>
> Looks like the quick fix is for Michael/Geert do not build uImage for
> xtensa on their automated build environments.
What would you do with an uImage file when there is no U-Boot to load
it?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH
On Tue, Apr 29, 2014 at 7:24 AM, Wolfgang Denk wrote:
> Dear Fabio Estevam,
>
> In message <1398746935-11855-1-git-send-email-feste...@gmail.com> you wrote:
>> From: Fabio Estevam
>>
>> Currently we get the following failure when trying to build a uImage for
>> extensa:
>>
>> $ ./tools/mkimage -A
Dear Fabio Estevam,
In message <1398746935-11855-1-git-send-email-feste...@gmail.com> you wrote:
> From: Fabio Estevam
>
> Currently we get the following failure when trying to build a uImage for
> extensa:
>
> $ ./tools/mkimage -A xtensa
...
> + { IH_ARCH_EXTENSA,"extensa",
Hi Fabio,
Thanks for the patch, but the name is actually 'xtensa' (without the
'e'). Would be great if you could change that.
Thanks,
-Chris
On 4/28/14, 9:48 PM, Fabio Estevam wrote:
From: Fabio Estevam
Currently we get the following failure when trying to build a uImage for
extensa:
$ .
From: Fabio Estevam
Currently we get the following failure when trying to build a uImage for
extensa:
$ ./tools/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, or
9 matches
Mail list logo