public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: vladimir.murzin@arm•com (Vladimir Murzin)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/4] arm/versatile: no-MMU support
Date: Wed, 7 Dec 2016 09:23:04 +0000	[thread overview]
Message-ID: <5847D4F8.1080108@arm.com> (raw)
In-Reply-To: <1481090912-29835-1-git-send-email-gerg@uclinux.org>

Hi Greg,

On 07/12/16 06:08, Greg Ungerer wrote:
> Does the ARM Versatile machine have a maintainer?
> I have CC'ed this patch set to those names reported by get_maintainer.
> I had no feedback on the first posting of this series back in August.
> 
> The following patches support configuring and building the versatile
> machine with a no-MMU kernel.
> 
> There is only a few minor changes required. It was previously possible
> in older kernels to build for versatile with CONFIG_MMU disabled, but
> the change to devicetree lost that capability. These changes make it
> possible again.
> 
> One patch is a fix for address translation (broken in older kernels too),
> two are build problems when CONFIG_MMU is disabled, and the last is the
> actuall configuration changes needed.
> 
> The motivation for this is that the versatile machine is well supported
> in qemu. And this provides an excellent platform for development and
> testing no-MMU support on ARM in general. With these patches applied
> it is possible to build and run a kernel with MMU disabled on qemu.

I'm wondering if my "Allow NOMMU for MULTIPLATFORM" series [1] work for you?

[1] https://www.spinics.net/lists/arm-kernel/msg546823.html

Cheers
Vladimir

> 
> Signed-off-by: Greg Ungerer <gerg@uclinux•org>
> ---
>  arch/arm/Kconfig                       |   10 ++++++++++
>  arch/arm/Kconfig.debug                 |    3 ++-
>  arch/arm/include/asm/mach/map.h        |    1 +
>  arch/arm/mach-versatile/Kconfig        |    3 ++-
>  arch/arm/mach-versatile/Makefile.boot  |    3 +++
>  arch/arm/mach-versatile/versatile_dt.c |    4 ++++
>  6 files changed, 22 insertions(+), 2 deletions(-)
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

  parent reply	other threads:[~2016-12-07  9:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07  6:08 [PATCH 0/4] arm/versatile: no-MMU support Greg Ungerer
2016-12-07  6:08 ` [PATCH 1/4] ARM: versatile: support no-MMU mode addressing Greg Ungerer
2016-12-07  6:08 ` [PATCH 2/4] ARM: versatile: define empty debug_ll_io_init() for no-MMU Greg Ungerer
2016-12-07  9:23 ` Vladimir Murzin [this message]
2016-12-07 13:57   ` [PATCH 0/4] arm/versatile: no-MMU support Greg Ungerer
2016-12-07 14:13     ` Vladimir Murzin
2016-12-07 14:21     ` Greg Ungerer
2016-12-07 14:27       ` Vladimir Murzin
2016-12-07 14:40         ` Greg Ungerer
2016-12-07 14:16 ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2016-09-26  0:52 Greg Ungerer

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=5847D4F8.1080108@arm.com \
    --to=vladimir.murzin@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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