mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Palmer <daniel@0x0f.com>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: geert@linux-m68k.org, christoph.plattner@gmx.at,
	 linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
	 arnd@kernel.org
Subject: Re: [RFC PATCH] m68k: nommu: Fix behaviour of io macros on non-CF
Date: Tue, 14 Apr 2026 21:55:40 +0900	[thread overview]
Message-ID: <CAFr9PXnfh6p_ajGSGX-MnKgToEdAW-3rPgOLKgaDXziKXNGfFQ@mail.gmail.com> (raw)
In-Reply-To: <ec4945ec-84fd-4462-b35d-79a04673107d@linux-m68k.org>

Hi Greg,

On Tue, 14 Apr 2026 at 21:18, Greg Ungerer <gerg@linux-m68k.org> wrote:
> This change, in this form at least, breaks most of the non-MMU ColdFire targets.
> Try compiling any of m5208evb, m5249evb, m5272c3, m5275evb, m5307c3 or
> m5407c3 defconfigs and you get build failures. Targets that do not have
> a PCI bus and so do not define IOMEMBASE will fail, which is most of them.

Oof, that's the second time I broke coldfire this week (I broke it
trying to make virtio work for m68k in u-boot too).
Your patch works for my mc68000 virt and dragonball builds. I will
build/boot test nommu CF in QEMU.

Thanks,

Daniel

  reply	other threads:[~2026-04-14 12:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04  2:46 Daniel Palmer
2026-04-13 16:52 ` Arnd Bergmann
2026-04-14  7:14   ` Geert Uytterhoeven
2026-04-14 12:18 ` Greg Ungerer
2026-04-14 12:55   ` Daniel Palmer [this message]
2026-04-14 13:24     ` Arnd Bergmann
2026-04-15 13:52       ` Greg Ungerer
2026-04-15 14:54         ` Arnd Bergmann
2026-04-17 14:11           ` Greg Ungerer
2026-04-17 16:36             ` Arnd Bergmann

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=CAFr9PXnfh6p_ajGSGX-MnKgToEdAW-3rPgOLKgaDXziKXNGfFQ@mail.gmail.com \
    --to=daniel@0x0f.com \
    --cc=arnd@kernel.org \
    --cc=christoph.plattner@gmx.at \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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
all inboxes | Powered by JetHome®