All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] linking rockchip-linux/u-boot.git with binutils-2.28
Date: Wed, 8 Mar 2017 17:32:45 -0500	[thread overview]
Message-ID: <20170308223245.GA25158@linux-uys3> (raw)
In-Reply-To: <20170308213321.GF19897@bill-the-cat>

On Wed 2017-03-08 @ 04:33:21 PM, Tom Rini wrote:
> Now, you've boot tested this, right? :)

Yes.

> Also, what board(s) show this problem exactly?

I'm working with the firefly-rk3288 board.

If it would be preferable to you, I have a patch for the meta-rockchip layer
that solves the problem for me. If you're leery about adding this for
everyone, I could just carry this patch locally and not affect u-boot upstream
at all.

I'm unfamiliar with the u-boot sources, is there a way to add a build flag
only for a specific board?

  reply	other threads:[~2017-03-08 22:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  7:39 [U-Boot] linking rockchip-linux/u-boot.git with binutils-2.28 Trevor Woerner
2017-03-08  8:22 ` Trevor Woerner
2017-03-08  8:43   ` Peter Robinson
2017-03-08 15:18     ` Simon Glass
2017-03-08 15:35       ` Tom Rini
2017-03-08 16:57         ` Trevor Woerner
2017-03-08 17:20           ` Tom Rini
2017-03-08 18:19             ` Trevor Woerner
2017-03-08 18:41               ` Tom Rini
2017-03-08 19:53                 ` Trevor Woerner
2017-03-08 21:33                   ` Tom Rini
2017-03-08 22:32                     ` Trevor Woerner [this message]
2017-03-08 22:33                       ` Trevor Woerner
2017-03-08 23:17                       ` Tom Rini
2017-03-09  4:36                         ` Trevor Woerner
2017-03-09 12:19                           ` Tom Rini
2017-03-08 16:43     ` Trevor Woerner
2017-03-08 16:51       ` Peter Robinson

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=20170308223245.GA25158@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.