From: Yannick GICQUEL <yannick.gicquel@open.eurogiciel.org>
To: linux-m68k@vger.kernel.org
Subject: [RFC 0/8] m5441x: mmu support patchset
Date: Wed, 8 Jul 2015 11:51:24 +0200 [thread overview]
Message-ID: <1436349092-2214-1-git-send-email-yannick.gicquel@gmail.com> (raw)
Hi all,
Here is a patchset proposal for MMU support on Coldfire 5441x serie.
This patchset allows building the mcfmmu on chip without FPU, enable the
elf binary support and report some code from m54xx to m5441x sources
files.
Also, it contains a proposal for uImage generation.
Functional status is OK on kernel v3.14.
But on v4.2-rc1, we observe a map_err exit fail in do_page_fault().
After bisecting, we point out the regression appears after the
vm_ops->map_pages() feature integration (introduced in 8c6e50b and later)
Your feedbacks are welcome on this.
Best Regards,
Yannick
Yannick GICQUEL (8):
m68k: coldfire: unlink FPU presence from MMU activation
m68k: fix build issue in setup_arch() when no FPU
m68k: add dummy dump_fpu() when FPU is not present
m68k: m5441x: add ColdFire 5441x CPU MMU memory init code
m68k: m5441x: fix ACR0 base address when MBAR is not present
m68k: m5441x: set rambar to end of SRAM physical addr space
m68k: mmu: add u-boot command line support in setup_arch()
m68k: uImage generation support
arch/m68k/Kconfig | 2 +-
arch/m68k/Kconfig.cpu | 4 +-
arch/m68k/Makefile | 8 +++-
arch/m68k/boot/Makefile | 45 ++++++++++++++++++++++
arch/m68k/coldfire/head.S | 9 +++++
arch/m68k/coldfire/m5441x.c | 47 +++++++++++++++++++++++
arch/m68k/include/asm/m54xxacr.h | 13 ++++++-
arch/m68k/kernel/process.c | 6 ++-
arch/m68k/kernel/setup_mm.c | 82 +++++++++++++++++++++++++++++++++++++++-
9 files changed, 209 insertions(+), 7 deletions(-)
create mode 100644 arch/m68k/boot/Makefile
--
1.9.1.286.g5172cb3
next reply other threads:[~2015-07-08 9:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 9:51 Yannick GICQUEL [this message]
2015-07-08 9:51 ` [RFC 1/8] m68k: coldfire: unlink FPU presence from MMU activation Yannick GICQUEL
2015-07-08 13:36 ` Greg Ungerer
2015-07-17 10:46 ` Yannick GICQUEL
2015-07-08 14:03 ` Geert Uytterhoeven
2015-07-08 14:12 ` Greg Ungerer
2015-07-08 14:20 ` Geert Uytterhoeven
2015-07-08 9:51 ` [RFC 2/8] m68k: fix build issue in setup_arch() when no FPU Yannick GICQUEL
2015-07-08 14:04 ` Geert Uytterhoeven
2015-07-08 9:51 ` [RFC 3/8] m68k: add dummy dump_fpu() when FPU is not present Yannick GICQUEL
2015-07-08 9:51 ` [RFC 4/8] m68k: m5441x: add ColdFire 5441x CPU MMU memory init code Yannick GICQUEL
2015-07-08 13:45 ` Greg Ungerer
2015-07-08 9:51 ` [RFC 5/8] m68k: m5441x: fix ACR0 base address when MBAR is not present Yannick GICQUEL
2015-07-08 9:51 ` [RFC 6/8] m68k: m5441x: set rambar to end of SRAM physical addr space Yannick GICQUEL
2015-07-08 13:53 ` Greg Ungerer
2015-07-17 10:47 ` Yannick GICQUEL
2015-07-08 9:51 ` [RFC 7/8] m68k: mmu: add u-boot command line support in setup_arch() Yannick GICQUEL
2015-07-08 14:03 ` Greg Ungerer
2015-07-08 9:51 ` [RFC 8/8] m68k: uImage generation support Yannick GICQUEL
2015-07-08 14:07 ` [RFC 0/8] m5441x: mmu support patchset Greg Ungerer
2015-07-17 10:30 ` Yannick GICQUEL
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=1436349092-2214-1-git-send-email-yannick.gicquel@gmail.com \
--to=yannick.gicquel@open.eurogiciel.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;
as well as URLs for NNTP newsgroup(s).