From: "Arnd Bergmann" <arnd@kernel.org>
To: "Michael Schmitz" <schmitzmic@gmail.com>,
"Niklas Schnelle" <schnelle@linux.ibm.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org,
"Heiko Carstens" <hca@linux.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] m68k: Handle HAS_IOPORT dependencies
Date: Wed, 03 Apr 2024 20:34:57 +0200 [thread overview]
Message-ID: <bf276f98-2712-4fcf-a119-f984a1aedbf2@app.fastmail.com> (raw)
In-Reply-To: <dd55afa6-8cb6-4e25-b720-d2df62dbb5e6@gmail.com>
On Wed, Apr 3, 2024, at 20:11, Michael Schmitz wrote:
> Niklas,
>
> how do you propose we handle legacy drivers that do depend on
> inb()/outb() functions (_not_ actual ISA I/O) on architectures that map
> inb()/outb() to MMIO functions?
>
> (In my case, that's at least ne.c - Geert ought to have a better
> overview what else does use inb()/outb() on m68k)
If a machine provides an inb()/outb() set of operations that
is actually used, it should set HAS_IOPORT.
For the Q40, it may be better in the long run to change the
drivers to just use MMIO directly though.
Arnd
next prev parent reply other threads:[~2024-04-03 18:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:28 [PATCH 0/1] m68k: Handle HAS_IOPORT dependencies Niklas Schnelle
2024-04-03 12:28 ` [PATCH 1/1] m68k: Let GENERIC_IOMAP depend on HAS_IOPORT Niklas Schnelle
2024-05-08 11:44 ` Geert Uytterhoeven
2024-04-03 18:11 ` [PATCH 0/1] m68k: Handle HAS_IOPORT dependencies Michael Schmitz
2024-04-03 18:34 ` Arnd Bergmann [this message]
2024-04-05 10:16 ` Geert Uytterhoeven
2024-04-05 11:24 ` Arnd Bergmann
2024-04-08 8:23 ` Geert Uytterhoeven
2024-04-05 18:36 ` Michael Schmitz
2024-04-05 20:13 ` Arnd Bergmann
2024-04-06 1:14 ` Michael Schmitz
2024-04-06 15:27 ` Arnd Bergmann
2024-04-06 20:09 ` Michael Schmitz
2024-04-08 8:19 ` Geert Uytterhoeven
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=bf276f98-2712-4fcf-a119-f984a1aedbf2@app.fastmail.com \
--to=arnd@kernel.org \
--cc=geert@linux-m68k.org \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.com \
--cc=schnelle@linux.ibm.com \
/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