Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: fabioestevam@yahoo.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: Impossible constraint in 'asm' in 2.6.35 build
Date: Fri, 6 Aug 2010 12:23:45 -0700 (PDT)	[thread overview]
Message-ID: <252875.53499.qm@web51004.mail.re2.yahoo.com> (raw)
In-Reply-To: <217515.74361.qm@web51005.mail.re2.yahoo.com>



--- On Fri, 8/6/10, Fabio Estevam <fabioestevam@yahoo.com> wrote:

> From: Fabio Estevam <fabioestevam@yahoo.com>
> Subject: Re: Impossible constraint in 'asm' in 2.6.35 build
> To: "Rob Herring" <robherring2@gmail.com>
> Cc: linux-arm-kernel at lists.infradead.org
> Date: Friday, August 6, 2010, 3:34 PM
> Rob,
> 
> --- On Fri, 8/6/10, Rob Herring <robherring2@gmail.com>
> wrote:
> 
> > From: Rob Herring <robherring2@gmail.com>
> > Subject: Re: Impossible constraint in 'asm' in 2.6.35
> build
> > To: "Fabio Estevam" <fabioestevam@yahoo.com>
> > Cc: linux-arm-kernel at lists.infradead.org
> > Date: Friday, August 6, 2010, 3:14 PM
> > Fabio,
> > 
> > It is due to this commit and using gcc 4.1.2:
> > 
> > commit 398aa66827155ef52bab58bebd24597d90968929
> > Author: Will Deacon <will.deacon@arm.com>
> > Date:???Thu Jul 8 10:59:16 2010 +0100
> > 
> > ? ? ARM: 6212/1: atomic ops: add memory
> > constraints to inline asm
> > 
> > It works fine for me with CS 4.3.3 toolchain.
> 
> I could get it to build in origin/master branch, but it
> fails for me in Sascha's origin/imx-for-2.6.36 branch.
> 
> Will use origin/master for now.

I made a mistake when upgrading the toolchain. origin/imx-for-2.6.36 branch builds fine now with arm-2010q1 toolchain.

Regards,

Fabio Estevam





      

      reply	other threads:[~2010-08-06 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06 17:32 Impossible constraint in 'asm' in 2.6.35 build Fabio Estevam
2010-08-06 18:14 ` Rob Herring
2010-08-06 18:34   ` Fabio Estevam
2010-08-06 19:23     ` Fabio Estevam [this message]

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=252875.53499.qm@web51004.mail.re2.yahoo.com \
    --to=fabioestevam@yahoo.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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