From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tegra20: add back USE_PRIVATE_LIBGCC
Date: Tue, 07 Aug 2012 11:00:32 -0600 [thread overview]
Message-ID: <502149B0.8020904@wwwdotorg.org> (raw)
In-Reply-To: <1344298788-7059-1-git-send-email-dev@lynxeye.de>
On 08/06/2012 06:19 PM, Lucas Stach wrote:
> As discussed here [http://patchwork.ozlabs.org/patch/158202/] we want to
> use USE_PRIVATE_LIBGCC still.
>
> However commit 5286f1ce dropped it regardless. Adding this back fixes a
> hang while handing over from SPL to U-Boot on Colibri T20.
This probably makes sense, but Allen should comment on this.
I wonder why I haven't seen any issue with this; perhaps SPL on all the
boards I tested ended up not using any libgcc functions? But in that
case, why would the Colibri board end up using them?
next prev parent reply other threads:[~2012-08-07 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 0:19 [U-Boot] [PATCH] tegra20: add back USE_PRIVATE_LIBGCC Lucas Stach
2012-08-07 17:00 ` Stephen Warren [this message]
2012-08-07 17:09 ` Lucas Stach
2012-08-07 17:43 ` Allen Martin
2012-08-07 17:53 ` Lucas Stach
2012-08-07 20:11 ` Allen Martin
2012-08-07 22:28 ` Allen Martin
2012-08-07 22:42 ` Lucas Stach
2012-08-07 23:34 ` Allen Martin
2012-08-07 18:36 ` Wolfgang Denk
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=502149B0.8020904@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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.