[U-Boot] [PATCH] tegra: override compiler flags for cmd_nvedit

[Allen Martin <amartin@nvidia.com>]

On Sat, May 05, 2012 at 01:01:22PM -0700, Wolfgang Denk wrote:
> Dear Allen Martin,
> 
> In message <1336163380-29679-1-git-send-email-amartin@nvidia.com> you wrote:
> > Override -march setting for tegra to -march=armv4t for cmd_nvedit.c
> > 
> > The recent change to use -march=armv7-a for armv7 caused a regression
> > on tegra because tegra starts boot on a arm7tdmi processor before
> > transferring control to the cortex-a9.  While still executing on the
> > arm7tdmi there is a call to getenv_ulong() that causes an illegal
> > instruction exception if cmd_nvedit is compiled for armv7.
> > 
> > Signed-off-by: Allen Martin <amartin@nvidia.com>
> > ---
> >  common/Makefile |    6 ++++++
> >  1 file changed, 6 insertions(+)
> 
> We definitely do not want to introduce board specific compile
> options in common code, and especially not on a per-file base.
> 

The other option is to compile all of tegra armv4t by modifying
arch/arm/cpu/armv7/config.mk, the resulting binary is about 300 bytes
larger though, which is a shame since it's only this one file that
really needs to be armv4t for the getenv_ulong() call.  Does this seem
like a more acceptable change though?

I see either solution as a temporary band-aid to get tegra booting
again until I finish the patch set to split out the armv4t code to a
SPL.  I hope to have a complete patch set ready to post for review in
a few days.

If you get a chance could you look over the following patches that I
posted recently:

tegra2: move tegra2 SoC code to arch/arm/cpu/tegra2-common
mkconfig: add support for SPL CPU

These are definately the most controversial patches in the patch set,
and I wanted to get some feedback if I'm headed in the right
direction.

Thanks,
-Allen



-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------