From: gang.chen@asianux.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [Suggestion] ARM:S5pv210: compiling issue for s5pv210 by using randconfig
Date: Wed, 17 Apr 2013 18:11:36 +0800 [thread overview]
Message-ID: <516E7558.4080005@asianux.com> (raw)
In-Reply-To: <20130417100136.GB19492@mudshark.cambridge.arm.com>
On 2013?04?17? 18:01, Will Deacon wrote:
> The problem here is that you've ended up targetting a platform (s5pv210)
> that selects CPU_V7. VFP is then subsequently selected, but CONFIG_MMU=n, so
> 7TDMI and 9TDMI (v4 CPUs, no VFP) are selectable. Selecting either of those,
> causes these warnings.
>
> Unfortunately, I'm not sure how best to fix this. Most of the !MMU CPUs are
> tied to a particular board (lots of `if ARCH_INTEGRATOR' predicates), but we
> don't want to do that for 7tdmi.
>
> If we could enforce the strict exclusion of {<= ARMv5} and {ARMv6+} in the
> Kconfig, that would solve your problem.
thank you very much for your analysing.
:-)
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2013-04-17 10:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 2:10 [Suggestion] ARM:S5pv210: compiling issue for s5pv210 by using randconfig Chen Gang
2013-04-03 9:46 ` Chen Gang
2013-04-03 10:10 ` Will Deacon
2013-04-03 10:29 ` Chen Gang
2013-04-17 9:25 ` Chen Gang
2013-04-17 10:01 ` Will Deacon
2013-04-17 10:11 ` Chen Gang [this message]
2013-04-17 10:53 ` Arnd Bergmann
2013-04-17 11:02 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-19 11:56 ` Chen Gang
2013-04-17 11:07 ` Chen Gang
2013-04-17 10:02 ` Russell King - ARM Linux
2013-04-17 10:17 ` Chen Gang
2013-04-22 6:13 ` Chen Gang
2013-04-24 4:12 ` [PATCH] ARM: Kconfig: let ARM9TDMI and ARM7TDMI invisible Chen Gang
2013-04-24 4:16 ` Chen Gang
2013-04-24 4:20 ` [PATCH v2] " Chen Gang
2013-04-24 17:46 ` Russell King - ARM Linux
2013-04-24 17:59 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-25 1:16 ` Chen Gang
2013-04-25 1:16 ` Chen Gang
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=516E7558.4080005@asianux.com \
--to=gang.chen@asianux.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).