public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tegra: override compiler flags for low level init code
Date: Mon, 4 Jun 2012 10:54:39 -0700	[thread overview]
Message-ID: <20120604175439.GA6692@nvidia.com> (raw)
In-Reply-To: <4FB193F5.5000704@wwwdotorg.org>

On Mon, May 14, 2012 at 04:23:33PM -0700, Stephen Warren wrote:
> On 05/14/2012 05:14 PM, Allen Martin wrote:
> > Override -march setting for tegra to -march=armv4t for files that are
> > necessary for low level init on tegra.
> > 
> > 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 are calls to getenv_ulong() and memset() that cause an
> > illegal instruction exception if compiled for armv7.
> > 
> > Signed-off-by: Allen Martin <amartin@nvidia.com>
> 
> Tested-by: Stephen Warren <swarren@wwwdotorg.org>
> 
> (This seems to be necessary to use gcc-4.6.1, but not gcc-4.5.3. The
> Whistler patches I just sent were tested with this fix in place)

Hi Tom, could you pick this up in u-boot-tegra?  Without it tegra is
currently broken in both u-boot-tegra and u-boot gits depending on the
compiler you use. 

-Allen
-- 
nvpublic

  reply	other threads:[~2012-06-04 17:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1336162232-19714-1-git-send-email-amartin@nvidia.com>
2012-05-14 20:25 ` [U-Boot] [PATCH v2] tegra: override compiler flags for cmd_nvedit Allen Martin
2012-05-14 23:14 ` [U-Boot] [PATCH] tegra: override compiler flags for low level init code Allen Martin
2012-05-14 23:23   ` Stephen Warren
2012-06-04 17:54     ` Allen Martin [this message]
2012-06-04 18:00       ` Stephen Warren
2012-06-04 18:06         ` Allen Martin
2012-06-04 18:10           ` Tom Warren

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=20120604175439.GA6692@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