Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Aarch64 u-boot with gcc .5x
Date: Mon, 28 Mar 2016 08:51:19 -0700	[thread overview]
Message-ID: <56F952F7.2010409@gmail.com> (raw)

Hello,

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?

kind regards,
Armin


             reply	other threads:[~2016-03-28 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 15:51 akuster808 [this message]
2016-03-28 18:20 ` Aarch64 u-boot with gcc .5x 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

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=56F952F7.2010409@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox