From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2: Fix the OMAP2 only build break seen with 2011+ ARM tool-chains
Date: Tue, 7 Feb 2012 21:33:43 -0800 [thread overview]
Message-ID: <20120208053343.GA1426@atomide.com> (raw)
In-Reply-To: <1328523587-21341-1-git-send-email-santosh.shilimkar@ti.com>
* Santosh Shilimkar <santosh.shilimkar@ti.com> [120206 01:48]:
> With the latest Sourcery G++ Lite 2011.03-41 and latest linaro
> tool-chains OMAP2 only build breaks with below error.
>
> arch/arm/mach-omap2/omap-smc.S: Assembler messages:
> arch/arm/mach-omap2/omap-smc.S:30: Error: selected processor does not support ARM mode `smc #0'
> arch/arm/mach-omap2/omap-smc.S:53: Error: selected processor does not support ARM mode `smc #0'
> arch/arm/mach-omap2/omap-smc.S:61: Error: selected processor does not support ARM mode `smc #0'
> arch/arm/mach-omap2/omap-smc.S:69: Error: selected processor does not support ARM mode `smc #0'
> arch/arm/mach-omap2/omap-smc.S:77: Error: selected processor does not support ARM mode `smc #0'
> make[1]: *** [arch/arm/mach-omap2/omap-smc.o] Error 1
>
> OMAP2 devices doesn't have the security support but the security support
> was getting built because of OMAP2PLUS. Don't build security code for
> OMAP2 devices.
>
> While at it, fix the secure-common line in the Makefile to use tabs
> instead of spaces.
>
> Reported-by: Kevin Hilman <khilman@ti.com>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Thanks, applying into fixes.
Regards,
Tony
prev parent reply other threads:[~2012-02-08 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 10:19 [PATCH] ARM: OMAP2: Fix the OMAP2 only build break seen with 2011+ ARM tool-chains Santosh Shilimkar
2012-02-08 5:33 ` Tony Lindgren [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=20120208053343.GA1426@atomide.com \
--to=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).