[U-Boot] [PATCH v2 46/58] avr32: Use generic global_data
Simon Glass
sjg at chromium.org
Thu Feb 28 02:22:04 CET 2013
Hi,
On Thu, Feb 14, 2013 at 8:15 AM, Tom Rini <trini at ti.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/14/2013 11:11 AM, Andreas Biemann wrote:
>> Hi Simon,
>>
>> On 02/14/2013 03:25 PM, Simon Glass wrote:
>>> Hi Andreas,
>>>
>>> On Thu, Feb 14, 2013 at 2:29 AM, Andreas Biemann
>>> <andreas.devel at googlemail.com> wrote:
>>>> Dear Simon Glass,
>>>>
>>>> On 12/14/2012 07:49 AM, Simon Glass wrote:
>>>>> Move avr32 over to use generic global_data.
>>>>>
>>>>> Signed-off-by: Simon Glass <sjg at chromium.org>
>>>>
>>>> this one produces compile warning in board.c for mimc200, I
>>>> will try to fix it but can not test it on real hardware (cc'ing
>>>> board maintainer).
>>>
>>> Actually these boards failed for be even before the patch:
>>>
>>> avr32: + hammerhead + atngw100mkii + grasshopper +
>>> favr-32-ezkit + atstk1006 + atstk1004 + atstk1003 + atstk1002
>>> + atngw100 + mimc200
>>>
>>> It might be my toolchain - can you suggest an avr32 toolchain to
>>> use?
>>
>> Not currently, I use a self patched OSELAS toolchain which is not
>> yet mainline. Maybe I should try to add avr32 toolchain to ELDK for
>> reference?
>
> The "short" answer is that if OpenEmbedded supports avr32 (and I'm a
> little rusty, but I see general avr32 bits and pieces) then yes,
> taking ELDK and building for AVR32 should be doable, or at least
> provide an interesting failure :)
Well if someone can point me to a binary or a build script I would
very much like to get an avr32 toolchain that fully works.
Thanks,
Simon
More information about the U-Boot
mailing list