From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: disabling MMU of ARMv7-A
Date: Fri, 28 Mar 2014 10:49:23 +0000 [thread overview]
Message-ID: <20140328104923.GH21330@arm.com> (raw)
In-Reply-To: <CAO1A-8DB_xAqAb2DOED3fmQ0GEOP4FFNyuZTVnjX+kiv4sRrtA@mail.gmail.com>
On Fri, Mar 28, 2014 at 07:23:45AM +0000, Marc C wrote:
> > However, ARMv7-A/R doesn't have such register. They can only control whether
> > use _HIGH_ vector or no
>
> Not entirely accurate. ARMv7-A, and the Cortex-A9, specify the Vector
> Base Address
> Register, or VBAR [1].
Good point, I missed this. It only works if SCTLR.V is 0 (so low
vectors).
--
Catalin
next prev parent reply other threads:[~2014-03-28 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 7:15 disabling MMU of ARMv7-A Chanho Park
2014-03-28 7:23 ` Marc C
2014-03-28 7:27 ` Chanho Park
2014-03-28 10:49 ` Catalin Marinas [this message]
2014-03-28 10:43 ` Catalin Marinas
2014-04-07 9:56 ` Dave Martin
2014-04-07 10:33 ` Russell King - ARM Linux
2014-04-07 17:16 ` 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=20140328104923.GH21330@arm.com \
--to=catalin.marinas@arm.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).