From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: CONFIG_CPU_SW_DOMAIN_PAN breakage on ARM11 MPCore
Date: Tue, 19 Jan 2016 16:27:49 +0100 [thread overview]
Message-ID: <12866783.yJ1maoGsrz@wuerfel> (raw)
In-Reply-To: <569E0796.9000302@openwrt.org>
On Tuesday 19 January 2016 10:53:26 Felix Fietkau wrote:
> root at OpenWrt:~# cat /proc/cpuinfo
> processor : 0
> model name : ARMv6-compatible processor rev 4 (v6l)
> BogoMIPS : 238.38
> Features : half thumb fastmult vfp edsp java tls
> CPU implementer : 0x41
> CPU architecture: 7
> CPU variant : 0x0
> CPU part : 0xb02
> CPU revision : 4
>
> processor : 1
> model name : ARMv6-compatible processor rev 4 (v6l)
> BogoMIPS : 239.61
> Features : half thumb fastmult vfp edsp java tls
> CPU implementer : 0x41
> CPU architecture: 7
> CPU variant : 0x0
> CPU part : 0xb02
> CPU revision : 4
I guess this means you run with the SMP patches from OpenWRT,
while upstream only supports uniprocessor mode and presumably doesn't
have this problem, right?
I see that Oxnas (supported in OpenWRT but not upstream) has the
slightly newer ARM11mpcore variant 0 / revision 5 ID. Is it easy for
you to test if this has the same problem?
Interestingly, the documentation at http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0360f/I65012.html
lists variant:0/revision:4 as the reported values for both r2p0 and r1p0
and it does not list any core having variant:0/revision:5.
Arnd
next prev parent reply other threads:[~2016-01-19 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 23:14 CONFIG_CPU_SW_DOMAIN_PAN breakage on ARM11 MPCore Felix Fietkau
2016-01-19 9:38 ` Russell King - ARM Linux
2016-01-19 9:53 ` Felix Fietkau
2016-01-19 15:27 ` Arnd Bergmann [this message]
2016-01-19 15:38 ` Felix Fietkau
2016-01-19 16:23 ` Russell King - ARM Linux
2016-01-20 19:57 ` Russell King - ARM Linux
2016-01-20 20:06 ` Felix Fietkau
2016-01-20 20:31 ` Arnd Bergmann
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=12866783.yJ1maoGsrz@wuerfel \
--to=arnd@arndb.de \
--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