From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/8] ARM: NOMMU: MPU updates
Date: Sat, 14 Oct 2017 15:37:21 +0100 [thread overview]
Message-ID: <20171014143721.GH20805@n2100.armlinux.org.uk> (raw)
In-Reply-To: <0edd802a-d596-5d46-ff53-97b1db1a453e@arm.com>
On Fri, Oct 13, 2017 at 10:40:39AM +0100, Vladimir Murzin wrote:
> On 13/10/17 10:24, Russell King - ARM Linux wrote:
> > Sorry, but I have no working MPS3 platform since it killed its uSD card
> > with all the FPGA bitstreams on. I'm waiting (since end of September)
> > for a replacement from ARM Ltd but there hasn't yet been any progress.
> >
> > Sure, I can replace the uSD card myself, but the problem is the contents
> > of the card.
>
> Thanks for prompt reply!
>
> I should say that board won't help you with testing this series since it
> implements different MPU model (I have patches for that too but they are
> on top of this series).
It assists as far as making sure the changes don't cause a
regression for the platform.
> I've been working closely with Alex and Andr?s (since they needed this for
> their Cortex-M7 platform) to make sure it works as expected. It was also
> tested with R-class FastModels.
>
> I intentionally kept CONFIG_ARM_MPU disabled by default for M-class
> (PATCH 6/8), so it won't interfere with existing bootloaders.
It looks like patch 6 will allow me to select ARM_MPU for the MPS3
config (by way of CPU_V7M being enabled). As I'm unable to test
what effect that has here, and I don't know when I'll be able to do
so, please check if not already done so.
> I'd be glad if you can review the series and give it a chance to sit in
> linux-next (I can provide a branch on top of yours for-next).
Please never provide a branch on top of my for-next, it's an "unstable"
commit in that it's regenerated from several sub-branches (fixes, misc,
devel-stable, and whatever other work I want to include in linux-next.)
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up
next prev parent reply other threads:[~2017-10-14 14:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 9:05 [PATCH v3 0/8] ARM: NOMMU: MPU updates Vladimir Murzin
2017-09-25 9:05 ` [PATCH v3 1/8] ARM: NOMMU: Move out MPU setup in separate module Vladimir Murzin
2017-10-14 14:22 ` Russell King - ARM Linux
2017-10-16 8:45 ` Vladimir Murzin
2017-09-25 9:05 ` [PATCH v3 2/8] ARM: NOMMU: Update MPU accessors to use cp15 helpers Vladimir Murzin
2017-09-25 9:05 ` [PATCH v3 3/8] ARM: NOMMU: Rework MPU to be mostly done in C Vladimir Murzin
2017-09-25 9:05 ` [PATCH v3 4/8] ARM: NOMMU: Disallow MPU for XIP Vladimir Murzin
2017-09-25 9:05 ` [PATCH v3 5/8] ARM: Kconfig: Kill CONFIG_VECTORS_BASE Vladimir Murzin
2017-09-25 9:05 ` [PATCH v3 6/8] ARM: V7M: Add support for MPU to M-class Vladimir Murzin
2017-09-25 9:05 ` [PATCH v3 7/8] ARM: NOMMU: Use more MPU regions to cover memory Vladimir Murzin
2017-09-25 9:05 ` [PATCH v3 8/8] ARM: NOMMU: Support MPU in XIP configuration Vladimir Murzin
2017-09-25 12:54 ` Alexandre Torgue
2017-09-25 14:43 ` Vladimir Murzin
2017-10-09 9:20 ` [PATCH v3 0/8] ARM: NOMMU: MPU updates Vladimir Murzin
2017-10-13 9:17 ` Vladimir Murzin
2017-10-13 9:24 ` Russell King - ARM Linux
2017-10-13 9:40 ` Vladimir Murzin
2017-10-14 14:37 ` Russell King - ARM Linux [this message]
2017-10-16 9:09 ` Vladimir Murzin
2017-10-17 14:05 ` Benjamin Gaignard
2017-10-17 14:13 ` Vladimir Murzin
2017-10-17 14:46 ` Russell King - ARM Linux
2017-10-17 14:56 ` Russell King - ARM Linux
2017-10-17 15:02 ` 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=20171014143721.GH20805@n2100.armlinux.org.uk \
--to=linux@armlinux.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;
as well as URLs for NNTP newsgroup(s).