All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo@sysam.it>
To: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68k: allow ColdFire m5441x parts to run with MMU enabled
Date: Sat, 15 Jul 2017 01:47:52 +0200	[thread overview]
Message-ID: <d1ce1669-0286-ebad-7c6c-e9dfe37c266c@sysam.it> (raw)
In-Reply-To: <bc3dc168-aaae-1271-b73b-4d649db5e301@sysam.it>

Hi Greg,

On 15/07/2017 01:21, Angelo Dureghello wrote:
> Hi Greg,
> 
> The Freescale ColdFire M5441x system-on-chip parts have full paged MMU
> hardware support. So far though we have only allowed them to be
> configured for use in non-MMU mode.
> 
> All required kernel changes to support operation of the M5441x parts
> with MMU enabled have been pushed into the kernel, so now we can allow
> it to be configured and used with the MMU enabled.
> 
> I don't actually have any M5441x based hardware so I can't do any real
> testing on this. The changes up to now were based on Yannick Gicquel
> initial patches to support this. Is anybody out there able to test
> this properly?  I won't push this any further until we have some
> confirmation that it all works as expected.
> 
> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
> ---
>   arch/m68k/Kconfig.cpu | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
> index d2219f30..4dc51c0 100644
> --- a/arch/m68k/Kconfig.cpu
> +++ b/arch/m68k/Kconfig.cpu
> @@ -283,7 +283,7 @@ config M548x
> 
>   config M5441x
>       bool "MCF5441x"
> -    depends on !MMU
> +    select MMU_COLDFIRE if MMU
>       select GENERIC_CLOCKEVENTS
>       select HAVE_CACHE_CB
>       help

forgot some useful info on my test:

- i built a 4.12 kernel from mainline (just pulled git master) and tested
to boot properly as no-mmu

- i have those entries in my defconfig:
....
CONFIG_BINFMT_FLAT=y
CONFIG_BINFMT_ZFLAT=y
CONFIG_BINFMT_SHARED_FLAT=y
CONFIG_BINFMT_MISC=y
....


I can help on debug when back from holidays, in 3 weeks.

Regards,
Angelo Dureghello

  reply	other threads:[~2017-07-14 23:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 23:21 Re:[PATCH] m68k: allow ColdFire m5441x parts to run with MMU enabled Angelo Dureghello
2017-07-14 23:47 ` Angelo Dureghello [this message]
2017-08-09 13:04   ` [PATCH] " Greg Ungerer
2017-08-09 15:32     ` Angelo Dureghello
2017-08-10  7:06       ` Greg Ungerer
2017-08-12 11:17         ` Angelo Dureghello
2017-08-14  4:16           ` Greg Ungerer
2017-08-17 15:02             ` Angelo Dureghello
2017-08-20 12:44               ` Greg Ungerer
2017-08-20 13:26                 ` Angelo Dureghello
2017-08-21  7:15                   ` Greg Ungerer
2017-08-21 14:58                     ` Angelo Dureghello
2017-08-21 20:11                       ` Geert Uytterhoeven
2017-08-22  0:15                         ` Angelo Dureghello
2017-08-22  0:35                     ` Angelo Dureghello
2017-08-22  1:08                       ` Greg Ungerer
2017-08-23  7:06                       ` Greg Ungerer
2017-08-27  0:31                         ` Angelo Dureghello
2017-08-31 22:38                           ` Angelo Dureghello
2017-09-01  7:49                             ` Geert Uytterhoeven
2017-09-01 13:21                               ` Greg Ungerer
2017-09-01 13:30                                 ` Geert Uytterhoeven
2017-09-01 22:08                                   ` Angelo Dureghello
2017-09-04  6:08                                     ` Greg Ungerer
2017-09-04 14:42                                       ` Angelo Dureghello
2017-09-07  2:01                                         ` Greg Ungerer
2017-09-07 20:23                                           ` Angelo Dureghello
2017-09-08  0:48                                             ` Greg Ungerer
2017-08-13  1:15         ` Angelo Dureghello
  -- strict thread matches above, loose matches on Subject: below --
2017-01-11 11:35 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=d1ce1669-0286-ebad-7c6c-e9dfe37c266c@sysam.it \
    --to=angelo@sysam.it \
    --cc=linux-m68k@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.