From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"Gregory CLEMENT" <gregory.clement@free-electrons.com>,
"Nicolas Pitre" <nicolas.pitre@linaro.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Måns Rullgård" <mans@mansr.com>,
linux-arm-msm@vger.kernel.org,
"Stephen Boyd" <sboyd@codeaurora.org>
Subject: Re: [PATCH] ARM: Runtime patch udiv/sdiv instructions into __aeabi_{u}idiv()
Date: Fri, 11 Dec 2015 23:51:45 +0100 [thread overview]
Message-ID: <1492057.yA5yAYfdog@wuerfel> (raw)
In-Reply-To: <20151211223415.GY8644@n2100.arm.linux.org.uk>
On Friday 11 December 2015 22:34:16 Russell King - ARM Linux wrote:
>
> __v7_pj4b_proc_info:
> - .long 0x562f5840
> - .long 0xfffffff0
> + .long 0x560f5800
> + .long 0xff0fff00
>
> So it was to include Armada 370. So this now brings up the question...
> what is the MIDR value used in Armada 370?
I've listed them in an earlier thread, here is the list again:
variant part revision name features
mmp2: 0 0x581 5 PJ4 idivt
dove: 0 0x581 5 PJ4 idivt
Armada 370 1 0x581 1 PJ4B idivt
mmp3: 2 0x584 2 PJ4-MP idiva idivt lpae
Armada XP 2 0x584 2 PJ4-MP idiva idivt lpae
Berlin 2 0x584 2 PJ4-MP idiva idivt lpae
So the original table was wrong because it failed to include PJ4B (Armada 370),
but the current version is wrong, because it also includes PJ4 (Dove and MMP2).
Arnd
next prev parent reply other threads:[~2015-12-11 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 6:26 [PATCH] ARM: Runtime patch udiv/sdiv instructions into __aeabi_{u}idiv() Nicolas Pitre
2015-12-11 9:24 ` Arnd Bergmann
2015-12-11 17:10 ` Nicolas Pitre
2015-12-11 17:22 ` Nicolas Pitre
2015-12-11 22:26 ` Arnd Bergmann
2015-12-11 23:57 ` Nicolas Pitre
2016-01-05 1:23 ` Stephen Boyd
2016-01-05 1:42 ` Nicolas Pitre
2016-01-08 2:44 ` Stephen Boyd
2016-01-12 19:09 ` Nicolas Pitre
2015-12-11 21:50 ` Arnd Bergmann
2015-12-11 22:00 ` Nicolas Pitre
2015-12-11 22:48 ` Arnd Bergmann
2015-12-11 22:34 ` Russell King - ARM Linux
2015-12-11 22:51 ` Arnd Bergmann [this message]
2015-12-12 0:01 ` Nicolas Pitre
2015-12-12 0:04 ` 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=1492057.yA5yAYfdog@wuerfel \
--to=arnd@arndb.de \
--cc=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mans@mansr.com \
--cc=nicolas.pitre@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=thomas.petazzoni@free-electrons.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