public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Anand Gadiyar <gadiyar@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Leif Lindholm <leif.lindholm@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: linux-next: omap2plus_defconfig does not build
Date: Tue, 19 Oct 2010 10:15:16 -0700	[thread overview]
Message-ID: <20101019171515.GB3038@atomide.com> (raw)
In-Reply-To: <a36d6a1047d959af6ea65cd7edacf6a8@mail.gmail.com>

* Anand Gadiyar <gadiyar@ti.com> [101013 06:14]:
> Building omap2plus_defconfig (which enables support for
> OMAP2420/2430/OMAP3
> and OMAP4 in one image), I get the following build error.
> 
>   CC      arch/arm/kernel/swp_emulate.o
> /tmp/ccg979qz.s: Assembler messages:
> /tmp/ccg979qz.s:343: Error: selected processor does not support ARM mode
> `ldrexb r6,[r5]'
> /tmp/ccg979qz.s:344: Error: selected processor does not support ARM mode
> `strexb r1,r3,[r5]'
> make[1]: *** [arch/arm/kernel/swp_emulate.o] Error 1
> make: *** [arch/arm/kernel] Error 2
> 
> I'm using CodeSourcery's 2010q1-202 toolchain based on gcc 4.4.1.
> 
> I haven't been following the lists closely the last few days, so I'm not
> sure if this is a known issue. Just reporting it for now.

This seems to be related to "ARM: Add SWP/SWPB emulation for ARMv7 processors (v5)"
where SWP_EMULATE is selected by default. For the omap2plus_defconfig in for-next
we now have CPU_V6 and CPU_V7 set with SMP and SMP_ON_UP.

Regards,

Tony

  reply	other threads:[~2010-10-19 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 13:23 linux-next: omap2plus_defconfig does not build Anand Gadiyar
2010-10-19 17:15 ` Tony Lindgren [this message]
2010-10-19 18:33   ` Gadiyar, Anand

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=20101019171515.GB3038@atomide.com \
    --to=tony@atomide.com \
    --cc=catalin.marinas@arm.com \
    --cc=gadiyar@ti.com \
    --cc=leif.lindholm@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.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