From: afzal.mohd.ma@gmail.com (Afzal Mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: nommu: R-class fixes
Date: Tue, 26 Apr 2016 20:53:37 +0530 [thread overview]
Message-ID: <20160426152337.GA10644@afzalpc> (raw)
In-Reply-To: <571F2427.5030003@arm.com> <5485255.0LNbKf2a8b@wuerfel>
Hi,
On Tue, Apr 26, 2016 at 09:17:43AM +0100, Vladimir Murzin wrote:
> I built myself, but there are prebild tools available at [1] although
> I've never tried them.
>
> It seems to me there have been internal patches to support FDPIC [2],
> but I don't know what happen afterwards :(
>
> [1] https://launchpad.net/gcc-arm-embedded
> [2]
> http://connect.linaro.org/resource/sfo15/sfo15-406-arm-fdpic-toolset-kernel-libraries-for-cortex-m-cortex-r-mmuless-cores/
Thank You, [2] gave some indigestion :), will take some to ...
On Tue, Apr 26, 2016 at 01:59:57PM +0200, Arnd Bergmann wrote:
> On Tuesday 26 April 2016 11:57:38 Vladimir Murzin wrote:
> and there are probably use cases for ARMv7-A without MMU.
My regular work is motor control related that uses RTOS, there was a
potential customer asking about running it with MMU, caches disabled
on A9. Probably the reason being they considering guranteed worst
case performance w/ caches enabled similar to that w/ caches disabled,
though that requirement was not in Linux.
> > Right they are quite close and shares a lot of code except MMU and MPU,
> > and I'd think without MMU/MPU such configurations are limited with UP
> I think one problem is that with MMU disabled ARMv7-A, you implicitly
> disable the caches and that is probably what you are thinking of for
> SMP support as well (atomic instructions need caches).
Have once tried to compile ARMv7-A w/o MMU, got entangled in a web of
Kconfig dependencies, iirc one among them was that with !MMU, MULTI_V7
platforms (AM335x, Vybrid A5 part) couldn't be selected, probably
because of SMP dependency, but that was on a older Kernel version.
Regards
afzal
next prev parent reply other threads:[~2016-04-26 15:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 11:43 [PATCH 0/3] ARM: nommu: R-class fixes Vladimir Murzin
2016-04-22 11:43 ` [PATCH 1/3] ARM: nommu: fix PMSAv7 setup Vladimir Murzin
2016-04-22 11:43 ` [PATCH 2/3] ARM: nommu: change memory reserve for the vectors Vladimir Murzin
2016-04-22 11:43 ` [PATCH 3/3] ARM: domain: move {set,get}_domain under config guard Vladimir Murzin
2016-04-27 10:49 ` [PATCH 3/3] ARM: domain: move {set, get}_domain " Russell King - ARM Linux
2016-04-27 12:16 ` Vladimir Murzin
2016-04-28 13:50 ` Russell King - ARM Linux
2016-04-28 14:44 ` Vladimir Murzin
2016-04-28 14:59 ` Russell King - ARM Linux
2016-04-28 15:06 ` Vladimir Murzin
2016-04-23 6:54 ` [PATCH 0/3] ARM: nommu: R-class fixes Afzal Mohammed
2016-04-25 7:55 ` Vladimir Murzin
2016-04-25 12:59 ` Arnd Bergmann
2016-04-25 13:30 ` Afzal Mohammed
2016-04-26 8:17 ` Vladimir Murzin
2016-04-26 8:17 ` Vladimir Murzin
2016-04-26 9:10 ` Arnd Bergmann
2016-04-26 10:57 ` Vladimir Murzin
2016-04-26 11:59 ` Arnd Bergmann
2016-04-26 12:24 ` Vladimir Murzin
2016-04-26 18:12 ` Arnd Bergmann
2016-04-27 9:10 ` Vladimir Murzin
2016-04-27 9:50 ` Arnd Bergmann
2016-04-27 10:55 ` Vladimir Murzin
2016-04-27 11:18 ` Arnd Bergmann
2016-04-26 15:23 ` Afzal Mohammed [this message]
2016-04-28 9:41 ` Maxime Coquelin
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=20160426152337.GA10644@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).