public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: linux-m68k@vger.kernel.org
Subject: [PATCH 0/8] m68k: prepare to support ColdFire M5441x MMU enabled
Date: Mon, 29 Aug 2016 21:43:16 +1000	[thread overview]
Message-ID: <1472471004-4580-1-git-send-email-gerg@linux-m68k.org> (raw)

The following changes are in preparation for supporting the ColdFire
M5441x SoC with its MMU enabled. (It is already supported in the no-MMU
mode).

Quite a few relate to the ability to run with no FPU hardware (and no
software emulation of FP). I have taken CONFIG_FPU to mean that we expect
a hardware FPU to be present - and we generate code to support that in
the kernel. If CONFIG_FPU is not defined we generate no support code
(so no use of FPU specific instructions). That is mostly what the code
already did, but not comepletely.

I don't actually enable the M5441x to run with MMU enabled in this
series. I don't have that hardware, so I can't verify that it actually
works. But these changes don't break the m547x, so I expect all is ok.
With the extra MMU enabling configuration line added you can cleanly
build for the M5441x with MMU enabled after this series though.

These patches are based on the ideas from Yannick Gicquel's
<yannick.gicquel@open.eurogiciel.org> patches from some time back.

Regards
Greg


 arch/m68k/Kconfig                     |    1
 arch/m68k/Kconfig.cpu                 |    6 +++++
 arch/m68k/coldfire/head.S             |    8 +++---
 arch/m68k/coldfire/m54xx.c            |   40 ----------------------------------
 arch/m68k/include/asm/m5441xsim.h     |    4 +++
 arch/m68k/include/asm/m54xxacr.h      |    2 -
 arch/m68k/include/asm/m54xxsim.h      |    4 +++
 arch/m68k/include/asm/mcfmmu.h        |    1
 arch/m68k/include/uapi/asm/bootinfo.h |    1
 arch/m68k/kernel/process.c            |    4 +--
 arch/m68k/kernel/setup_mm.c           |    5 ++--
 arch/m68k/mm/mcfmmu.c                 |   31 +++++++++++++++++++++++++-
 12 files changed, 57 insertions(+), 50 deletions(-)

             reply	other threads:[~2016-08-29 11:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 11:43 Greg Ungerer [this message]
2016-08-29 11:43 ` [PATCH 1/8] m68k: move CONFIG_FPU set to per-CPU configuration Greg Ungerer
2016-08-29 11:43 ` [PATCH 2/8] m68k: set appropriate machine type for m5411x SoC platforms Greg Ungerer
2016-08-29 11:43 ` [PATCH 3/8] m68k: report correct FPU type on ColdFire MMU platforms Greg Ungerer
2016-08-29 11:43 ` [PATCH 4/8] m68k: move ColdFire _bootmem_alloc code Greg Ungerer
2016-08-29 11:43 ` [PATCH 5/8] m68k: generalize io memory region setup for ColdFire ACR registers Greg Ungerer
2016-08-29 11:43 ` [PATCH 6/8] m68k: always make available dump_fpu() Greg Ungerer
2016-08-29 11:43 ` [PATCH 7/8] m68k: only generate FPU instructions of CONFIG_FPU Greg Ungerer
2016-08-29 12:53   ` Geert Uytterhoeven
2016-08-29 23:58     ` Greg Ungerer
2016-08-30  6:26       ` Geert Uytterhoeven
2016-08-30  7:30         ` Greg Ungerer
2016-08-29 11:43 ` [PATCH 8/8] m68k: don't panic if no hardware FPU defined 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=1472471004-4580-1-git-send-email-gerg@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox