From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/9] tegra: enable SPL build for seaboard
Date: Tue, 22 May 2012 12:02:10 -0700 [thread overview]
Message-ID: <20120522190210.GG30009@nvidia.com> (raw)
In-Reply-To: <4FBBC7D9.5030607@wwwdotorg.org>
On Tue, May 22, 2012 at 10:07:37AM -0700, Stephen Warren wrote:
> On 05/18/2012 04:24 PM, Allen Martin wrote:
> > On Mon, May 14, 2012 at 10:06:40PM -0700, Stephen Warren wrote:
> >> On 05/10/2012 01:02 AM, Allen Martin wrote:
> ...
> >> Perhaps we can just create a new tegra_spl board for the SPL rather than
> >> having an SPL variant for each board. Still, I don't know how we'd
> >> represent the UART differences if we did that though.
> >
> > I tossed out that idea as part of the discussion about using a
> > separate toolchain for the SPL, but Wolfgang shot it down:
> >
> > http://lists.denx.de/pipermail/u-boot/2012-April/122248.html
>
> Is that the right link? That message seems to be talking about a
> CROSS_COMPILE_SPL variable rather than having a separate boards.cfg
> entry for a Tegra SPL.
This was the piece I was referring to, which was a conversation about
exactly this topic (armv4 SPL and armv7 u-boot):
> > The architecture seems harder to fix. It seems like I really have to
> > have two entries in boards.cfg, which means two passes of config/make.
>
> This should be not needed; I also do not think this would be an
> acceptable approach.
-Allen
--
nvpublic
next prev parent reply other threads:[~2012-05-22 19:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 7:02 [U-Boot] [PATCH 0/9] split tegra arm7 code into separate SPL Allen Martin
2012-05-10 7:02 ` [U-Boot] [PATCH 1/9] tegra2: move tegra2 SoC code to arch/arm/cpu/tegra2-common Allen Martin
2012-05-10 7:02 ` [U-Boot] [PATCH 2/9] mkconfig: add support for SPL CPU Allen Martin
2012-05-10 7:02 ` [U-Boot] [PATCH 3/9] ARM: Fix arm720t SPL build Allen Martin
2012-05-10 7:02 ` [U-Boot] [PATCH 4/9] tegra: Add SPL build support to tegra boards Allen Martin
2012-05-15 4:55 ` Stephen Warren
2012-05-18 22:42 ` Allen Martin
2012-05-10 7:02 ` [U-Boot] [PATCH 5/9] ARM: add tegra support to arm720t Allen Martin
2012-05-15 5:03 ` Stephen Warren
2012-05-18 22:37 ` Allen Martin
2012-05-22 17:10 ` Stephen Warren
2012-05-22 19:14 ` Allen Martin
2012-05-10 7:02 ` [U-Boot] [PATCH 6/9] tegra: enable SPL build for seaboard Allen Martin
2012-05-15 5:06 ` Stephen Warren
2012-05-18 22:24 ` Allen Martin
2012-05-22 17:07 ` Stephen Warren
2012-05-22 19:02 ` Allen Martin [this message]
2012-05-10 7:02 ` [U-Boot] [PATCH 7/9] tegra: add u-boot.t2 target Allen Martin
2012-05-15 5:08 ` Stephen Warren
2012-05-18 22:14 ` Allen Martin
2012-05-10 7:02 ` [U-Boot] [PATCH 8/9] tegra2: Remove CPU init code from tegra2 u-boot Allen Martin
2012-05-10 7:02 ` [U-Boot] [PATCH 9/9] tegra2: Remove USE_PRIVATE_LIBGCC and armv4t build flags Allen Martin
2012-05-15 5:11 ` Stephen Warren
2012-05-18 22:13 ` Allen Martin
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=20120522190210.GG30009@nvidia.com \
--to=amartin@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox