linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: afzal.mohd.ma@gmail.com (afzal mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 5/5] ARM: NOMMU: Support PMSAv8 MPU
Date: Tue, 19 Dec 2017 11:41:45 +0530	[thread overview]
Message-ID: <20171219061145.GA8023@afzalpc> (raw)
In-Reply-To: <7c64f605-462b-728c-36d7-e8380c3f16db@arm.com>

Hi,

On Mon, Dec 18, 2017 at 11:47:04AM +0000, Vladimir Murzin wrote:

> > Is there a public ARMv8-R architecture reference manual available ?,

> you might get PMSA-v8 related information from Cortex-R52 TRM [1].
> 
> [1] https://developer.arm.com/docs/100026/latest/preface

Thanks Vladimir.

Got a ARMv8-R ARM supplement to ARMv8-A ARM,
https://static.docs.arm.com/ddi0568/a/DDI0568A_b_armv8_r_supplement.pdf

> Not sure why it is not there yet

Cortex-R mafia again ;)

afzal

  reply	other threads:[~2017-12-19  6:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 17:02 [RFC PATCH 0/5] Introduce PMSAv8 memory protection unit Vladimir Murzin
2017-12-13 17:02 ` [RFC PATCH 1/5] ARM: NOMMU: Move PMSAv7 MPU under it's own namespace Vladimir Murzin
2017-12-13 17:02 ` [RFC PATCH 2/5] ARM: NOMMU: Reorganise __setup_mpu Vladimir Murzin
2017-12-13 17:02 ` [RFC PATCH 3/5] ARM: NOMMU: Postpone MPU activation till __after_proc_init Vladimir Murzin
2017-12-13 17:02 ` [RFC PATCH 4/5] ARM: NOMMU: Make _stext and _end meet PMSAv8 alignment restrictions Vladimir Murzin
2017-12-13 17:02 ` [RFC PATCH 5/5] ARM: NOMMU: Support PMSAv8 MPU Vladimir Murzin
2017-12-14  5:01   ` afzal mohammed
2017-12-18 11:47     ` Vladimir Murzin
2017-12-19  6:11       ` afzal mohammed [this message]
2017-12-15 10:21 ` [RFC PATCH 0/5] Introduce PMSAv8 memory protection unit Szemző András
2017-12-15 10:29   ` Vladimir Murzin

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=20171219061145.GA8023@afzalpc \
    --to=afzal.mohd.ma@gmail.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).