From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] ARM: tegra: Prepare for 64-bit support
Date: Fri, 20 Mar 2015 10:24:36 -0600 [thread overview]
Message-ID: <550C49C4.6090300@wwwdotorg.org> (raw)
In-Reply-To: <1426854262-1248-1-git-send-email-thierry.reding@gmail.com>
On 03/20/2015 06:24 AM, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Move various selects from the TEGRA symbol to the symbols for 32-bit
> Tegra boards. This is necessary because these settings do not extend
> to U-Boot for 64-bit Tegra SoCs. Also tie the private libgcc build
> to SPL, it isn't needed on 64-bit Tegra.
I vaguely recall Masahiro enabling SPL for all Tegra builds recently for
some reason...
next prev parent reply other threads:[~2015-03-20 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 12:24 [U-Boot] [PATCH 1/6] ARM: tegra: Prepare for 64-bit support Thierry Reding
2015-03-20 12:24 ` [U-Boot] [PATCH 2/6] ARM: tegra: Disable SPL and non-cached memory on 64-bit Thierry Reding
2015-03-20 16:26 ` Stephen Warren
2015-03-20 17:09 ` Tom Rini
2015-03-20 18:26 ` Stephen Warren
2015-03-20 12:24 ` [U-Boot] [PATCH 3/6] ARM: tegra: Use standard cache enable for 64-bit Thierry Reding
2015-03-20 12:24 ` [U-Boot] [PATCH 4/6] ARM: tegra: Restrict usable RAM to 32-bit on 64-bit SoCs Thierry Reding
2015-03-20 12:24 ` [U-Boot] [PATCH 5/6] ARM: tegra: Skip FDT and initrd relocation on 64-bit Thierry Reding
2015-03-20 12:24 ` [U-Boot] [PATCH 6/6] ARM: tegra: Make pinmux.h standalone includible Thierry Reding
2015-03-20 16:30 ` Stephen Warren
2015-03-20 16:24 ` Stephen Warren [this message]
2015-03-25 4:02 ` [U-Boot] [PATCH 1/6] ARM: tegra: Prepare for 64-bit support Masahiro Yamada
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=550C49C4.6090300@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.