From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: tcm: Don't crash when TCM banks are protected by TrustZone
Date: Tue, 2 Jun 2015 16:35:48 +0100 [thread overview]
Message-ID: <20150602153548.GG2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <E0CBFB71-15B1-4C83-8B97-AF1C5CA48B98@smart-africa.com>
On Tue, Jun 02, 2015 at 05:21:11PM +0200, Michael van der Westhuizen wrote:
> It?s almost depressing how quickly you grokked that!
Quite simple really:
$ cat > t.s
.word 0xee190f11
.word 0xee190f31
$ arm-linux-as -o t.o t.s
$ arm-linux-objdump -d t.o
...
00000000 <.text>:
0: ee190f11 mrc 15, 0, r0, cr9, cr1, {0}
4: ee190f31 mrc 15, 0, r0, cr9, cr1, {1}
Those two words being the values which fit the word and mask you
specified, omitting the usual location for Rd (which is normally bits
12:16 in ARM instructions). Of course, a couple more words would
confirm that.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-06-02 15:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 9:36 [PATCH] arm: tcm: Don't crash when TCM banks are protected by TrustZone Michael van der Westhuizen
2015-05-28 10:16 ` Dave Martin
2015-05-28 11:32 ` Michael van der Westhuizen
2015-05-28 13:32 ` Dave Martin
2015-05-28 13:37 ` Michael van der Westhuizen
2015-05-28 13:54 ` [PATCH v2] " Michael van der Westhuizen
2015-06-02 11:16 ` Linus Walleij
2015-06-02 14:52 ` Russell King - ARM Linux
2015-06-02 15:21 ` Michael van der Westhuizen
2015-06-02 15:35 ` Russell King - ARM Linux [this message]
2015-06-02 15:10 ` [PATCH v3] " Michael van der Westhuizen
2015-06-04 10:40 ` Dave Martin
2015-06-04 11:35 ` Michael van der Westhuizen
2015-06-04 11:58 ` [PATCH v4] " Michael van der Westhuizen
2015-06-04 12:14 ` Linus Walleij
2015-06-04 13:43 ` Dave Martin
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=20150602153548.GG2067@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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