All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Aarch64 u-boot with gcc .5x
Date: Mon, 28 Mar 2016 15:08:22 -0700	[thread overview]
Message-ID: <56F9AB56.2010707@gmail.com> (raw)
In-Reply-To: <CAP9ODKrhWXSrSR5HhWy0gRTzJ896EMuGZb1qJ9VnDV29VJjv7g@mail.gmail.com>



On 03/28/2016 02:17 PM, Otavio Salvador wrote:
> On Mon, Mar 28, 2016 at 5:52 PM, akuster808 <akuster808@gmail.com> wrote:
>> On 03/28/2016 11:20 AM, Otavio Salvador wrote:
>>> On Mon, Mar 28, 2016 at 12:51 PM, akuster808 <akuster808@gmail.com> wrote:
>>>> I have an arm64 odroid c2 board.  If I build u-boot with the current OE
>>>> 5.3 gcc it hangs at kernel load time. If I use 4.9 gcc it works fine. A
>>>> 5.3 built kernel boots fine with a 4.9 built u-boot.
>>>>
>>>> The vendor supplied u-boot is hacked up and am leaning it that direction
>>>> as the culprit so I am looking for data points.
>>>>
>>>> Is anyone using a current u-boot with 5.3 gcc on an arm64 machine? if
>>>> so, any special tweaks to get that combo to work?
>>>
>>> I am using one ARM 64 SoC with GCC 5.2 at this moment and it works
>>> fine. What U-Boot version is the fork based on?
>>
>> 2015.01
> 
> Please try to use GCC 5.2 and see if it makes any difference. The BSP
> I am referring to is currently using it and it is working fine.
> 
> The forked version is the same. Of course, it may have changes which
> hides or solve the issue but it is a hint anyway.
ok. will try this next.

kind regards,
Armin


      reply	other threads:[~2016-03-28 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 15:51 Aarch64 u-boot with gcc .5x akuster808
2016-03-28 18:20 ` Otavio Salvador
2016-03-28 20:08   ` Stephen Arnold
2016-03-28 20:52   ` akuster808
2016-03-28 21:17     ` Otavio Salvador
2016-03-28 22:08       ` akuster808 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56F9AB56.2010707@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.