From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jonas Jensen <jonas.jensen@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, arm@kernel.org,
linux-kernel@vger.kernel.org, ulli.kroll@googlemail.com,
arnd@arndb.de, olof@lixom.net
Subject: Re: [PATCH] ARM: reinsert ARCH_MULTI_V4 Kconfig option
Date: Fri, 13 Dec 2013 09:56:55 +0000 [thread overview]
Message-ID: <20131213095655.GB4360@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1386922149-4561-1-git-send-email-jonas.jensen@gmail.com>
On Fri, Dec 13, 2013 at 09:09:09AM +0100, Jonas Jensen wrote:
> CPU_FA526 lacks thumb state support and doesn't get along with some
> of the options enabled by ARCH_MULTI_V4T.
>
> More specifically it doesn't get along with CPU_ARM920T:
>
> CPU_ABRT_EV4T
> CPU_CACHE_V4WT
> CPU_COPY_V4WB
> CPU_TLB_V4WBI
Having these selected doesn't change how the kernel is compiled or how
the kernel uses the code which these provide. These mainly control
which files are built.
They also control indirectly how the code is called - but the ultimate
decision is made by the CPU which is detected and the block in
__fa526_proc_info.
So, having these symbols enabled (provided the right ones for FA526 are
also enabled) makes no difference. So I don't buy your explanation.
next prev parent reply other threads:[~2013-12-13 9:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 8:09 Jonas Jensen
2013-12-13 9:56 ` Russell King - ARM Linux [this message]
2013-12-13 10:51 ` Jonas Jensen
2013-12-13 11:39 ` Russell King - ARM Linux
2013-12-13 13:33 ` Jonas Jensen
2014-04-09 14:54 ` Jonas Jensen
2014-04-09 15:04 ` Uwe Kleine-König
2014-04-09 15:09 ` Russell King - ARM Linux
2014-04-09 15:06 ` Russell King - ARM Linux
2014-04-09 15:13 ` Uwe Kleine-König
2014-04-09 15:27 ` Russell King - ARM Linux
2014-04-09 15:50 ` Arnd Bergmann
2014-04-09 16:01 ` Russell King - ARM Linux
2014-04-10 8:04 ` Jonas Jensen
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=20131213095655.GB4360@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=jonas.jensen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=ulli.kroll@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®