All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gadiyar, Anand" <gadiyar@ti.com>
To: Tony Lindgren <tony@atomide.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: Wed, 20 Oct 2010 00:03:11 +0530	[thread overview]
Message-ID: <AANLkTikGkpx8Pd9uPSyQus2FibyU=zUjxFkwJnofFO9q@mail.gmail.com> (raw)
In-Reply-To: <20101019171515.GB3038@atomide.com>

On Tue, Oct 19, 2010 at 10:45 PM, Tony Lindgren <tony@atomide.com> wrote:
> * 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.
>

I had forgotten I'd reported this earlier. I reported the build break
again today, and Catalin provided this patch [1] which solves the
build issue.

- Anand

[1] http://marc.info/?t=128748412500003&r=1&w=2
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: gadiyar@ti.com (Gadiyar, Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: omap2plus_defconfig does not build
Date: Wed, 20 Oct 2010 00:03:11 +0530	[thread overview]
Message-ID: <AANLkTikGkpx8Pd9uPSyQus2FibyU=zUjxFkwJnofFO9q@mail.gmail.com> (raw)
In-Reply-To: <20101019171515.GB3038@atomide.com>

On Tue, Oct 19, 2010 at 10:45 PM, Tony Lindgren <tony@atomide.com> wrote:
> * 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.
>

I had forgotten I'd reported this earlier. I reported the build break
again today, and Catalin provided this patch [1] which solves the
build issue.

- Anand

[1] http://marc.info/?t=128748412500003&r=1&w=2

  reply	other threads:[~2010-10-19 18:33 UTC|newest]

Thread overview: 6+ 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-13 13:23 ` Anand Gadiyar
2010-10-19 17:15 ` Tony Lindgren
2010-10-19 17:15   ` Tony Lindgren
2010-10-19 18:33   ` Gadiyar, Anand [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='AANLkTikGkpx8Pd9uPSyQus2FibyU=zUjxFkwJnofFO9q@mail.gmail.com' \
    --to=gadiyar@ti.com \
    --cc=catalin.marinas@arm.com \
    --cc=leif.lindholm@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.