From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 00/13] split tegra20 arm7 code into separate SPL
Date: Mon, 25 Jun 2012 16:20:49 -0700 [thread overview]
Message-ID: <20120625232049.GB13862@nvidia.com> (raw)
In-Reply-To: <4FE8EE7C.7000808@wwwdotorg.org>
On Mon, Jun 25, 2012 at 04:04:28PM -0700, Stephen Warren wrote:
> On 06/25/2012 04:55 PM, Allen Martin wrote:
> > This patch series fixes a long standing problem with the tegra20
> > u-boot build. Tegra20 contains an ARM7TDMI boot processor and a
> > Cortex A9 main processor. Prior to this patch series this was
> > accomplished by #ifdefing out any armv7 code from the early boot
> > sequence and creating a single binary that runs on both both the
> > ARM7TDMI and A9. This was very fragile as changes to compiler options
> > or any additions or rearranging of the early boot code could add
> > additional armv7 specific code causing it to fail on the ARM7TDMI.
> >
> > This patch series pulls all the armv4t code out into a separate SPL
> > that does nothing more than initialize the A9 and transfer control to
> > it. The resultint SPL and armv7 u-boot are concatenated together into
> > a single image.
> >
> > This patch series is also available from:
> > git://github.com/arm000/u-boot.git
> > branch: tegra-spl-v5
> >
> > Changes:
> > v5:
> > - added missing mkdir rules in all tegra20 board Makefiles that
> > include common code and changed them to be unconditional
> > - make new u-boot-dtb-t2.bin rule default for tegra20 and copy
> > resulting binary over u-boot.bin
>
> Doesn't that then destroy the original u-boot.bin so it can't be inspected?
Good point, perhaps I should back it up first? I was trying to
respond to Tom's objection that people expect the final binary to be
u-boot.bin, and it's confusing if it's not. I don't really want to
mess with the standard u-boot.bin rule, so how about backing it up to
"u-boot-tegra.bin" and making "u-boot.bin" be the final image ?
-Allen
--
nvpublic
next prev parent reply other threads:[~2012-06-25 23:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 22:55 [U-Boot] [PATCH v5 00/13] split tegra20 arm7 code into separate SPL Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 01/13] tegra20: rename tegra2 -> tegra20 Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 02/13] tegra20: move tegra20 SoC code to arch/arm/cpu/tegra20-common Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 03/13] tegra20: rename CONFIG_MACH_TEGRA_GENERIC Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 04/13] tegra20: tec: add tegra20-common-post.h Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 05/13] tegra20: make board mkdir commands unconditional Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 06/13] mkconfig: add support for SPL CPU Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 07/13] ARM: Fix arm720t SPL build Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 08/13] tegra20: remove timer_init from " Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 09/13] ARM: add tegra20 support to arm720t Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 10/13] tegra20: add u-boot-t2.bin target Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 11/13] tegra20: move SDRAM param save to later in boot Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 12/13] tegra20: enable SPL for tegra20 boards Allen Martin
2012-06-25 22:55 ` [U-Boot] [PATCH v5 13/13] tegra20: Remove armv4t build flags Allen Martin
2012-06-25 23:04 ` [U-Boot] [PATCH v5 00/13] split tegra20 arm7 code into separate SPL Stephen Warren
2012-06-25 23:20 ` Allen Martin [this message]
2012-06-25 23:40 ` Tom Warren
2012-06-26 1:53 ` Marek Vasut
2012-07-02 23:47 ` Tom Warren
2012-07-19 20:14 ` Simon Glass
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=20120625232049.GB13862@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