On Sun, May 13, 2012 at 10:24:19PM -0700, Mike Frysinger wrote:
> On Monday 07 May 2012 12:36:00 Allen Martin wrote:
> > The other option is to compile all of tegra armv4t by modifying
> > arch/arm/cpu/armv7/config.mk
>
> no it's not. arch and board config.mk get sourced, so you can put this
> b
On Monday 07 May 2012 12:36:00 Allen Martin wrote:
> On Sat, May 05, 2012 at 01:01:22PM -0700, Wolfgang Denk wrote:
> > Allen Martin 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 Sat, May 05, 2012 at 01:01:22PM -0700, Wolfgang Denk wrote:
> Dear Allen Martin,
>
> In message <1336163380-29679-1-git-send-email-amar...@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 ca
Dear Allen Martin,
In message <1336163380-29679-1-git-send-email-amar...@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 proces
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
5 matches
Mail list logo