[U-Boot] [PATCH v5 00/13] split tegra20 arm7 code into separate SPL

[Allen Martin]

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