Thread (19 messages) 19 messages, 7 authors, 2025-06-08

Re: [PATCH 6/6] m68k/nommu: stop using GENERIC_IOMAP

From: "Arnd Bergmann" <arnd@arndb.de>
Date: 2025-03-24 14:40:35
Also in: linux-alpha, linux-arch, linux-m68k, linux-mips, linux-sh, lkml

On Mon, Mar 24, 2025, at 14:50, Greg Ungerer wrote:
On 24/3/25 18:02, Arnd Bergmann wrote:
quoted
On Mon, Mar 24, 2025, at 02:33, Greg Ungerer wrote:
quoted
On 15/3/25 20:59, Arnd Bergmann wrote:
Does this fixup work for you?
Yes, this looks good, works for me.
Feel free to add this if you like:

Acked-by: Greg Ungerer <gerg@linux-m68k.org>
Added now, thanks!
quoted
On a related note, I'm curious about how the MCF54xx chips are
used in practice, as I see that they are the only coldfire chips
with PCI and they all have an MMU. Are there actual users of these
chips that have PCI but choose not to use the MMU?
No, I think everyone with these uses them with MMU enabled.

It is probably more of an historical curiosity to use them with
the MMU disabled. That supported pre-dated mainline kernels having
full ColdFire MMU support by a good few years.
Ok, good to know. Given that there are no other chips that allow
PCI on !MMU kernels, I wonder if we should just make PCI itself
depend on MMU, and remove the "depends on MMU" for any PCI
drivers that currently have it.

There is no fundamental dependency here, but it is something that
breaks occasionally because of in-kernel interfaces that don't
work as expected on !MMU configurations, and with an extra
dependency we could stop fixing those.

      Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help