linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Palmer <daniel@thingy.jp>
To: linux-m68k@lists.linux-m68k.org, linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Daniel Palmer <daniel@thingy.jp>
Subject: [RFC PATCH 0/5] PCI on the Amiga 4000
Date: Tue,  7 Oct 2025 18:23:08 +0900	[thread overview]
Message-ID: <20251007092313.755856-1-daniel@thingy.jp> (raw)

This series adds a driver for the Mediator 4000 PCI
bridge for the Amiga 4000.

Since this is my first PCI driver it's probably awful
so this is an RFC and also there is one interesting
unsolved bit:

As far as I can tell the Mediator 4000 cannot do DMA
between the normal memory and the PCI cards but PCI cards
can DMA between themselves. In the AmigaOS drivers a
bounce buffer is allocated on one of the cards that contains
memory, like a graphics card, and that is used for PCI
DMA. I'm not sure if that's even possible to do in Linux?

I've managed to use a network card that doesn't need DMA
so far, but I'm having trouble getting a Voodoo 3000 or
Radeon 9250 graphics card to come up properly. I guess
no one tests their cutting edge graphics drivers on non-x86
machines. ;)

Daniel Palmer (5):
  m68k: Adjust the pci io range
  m68k: Increase number of IRQs for Amiga to allow for PCI
  m68k: amiga: Allow PCI
  zorro: Add ids for Elbox Mediator 4000
  PCI: Add driver for Elbox Mediator 4000 Zorro->PCI bridge

 arch/m68k/Kconfig.machine                 |   1 +
 arch/m68k/include/asm/io_mm.h             |   9 +-
 arch/m68k/include/asm/irq.h               |   4 +-
 drivers/pci/controller/Kconfig            |  11 +
 drivers/pci/controller/Makefile           |   1 +
 drivers/pci/controller/pci-mediator4000.c | 314 ++++++++++++++++++++++
 drivers/zorro/zorro.ids                   |   2 +
 7 files changed, 338 insertions(+), 4 deletions(-)
 create mode 100644 drivers/pci/controller/pci-mediator4000.c

-- 
2.51.0


             reply	other threads:[~2025-10-07  9:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07  9:23 Daniel Palmer [this message]
2025-10-07  9:23 ` [RFC PATCH 1/5] m68k: Adjust the pci io range Daniel Palmer
2025-10-07  9:23 ` [RFC PATCH 2/5] m68k: Increase number of IRQs for Amiga to allow for PCI Daniel Palmer
2025-10-07  9:23 ` [RFC PATCH 3/5] m68k: amiga: Allow PCI Daniel Palmer
2025-10-07  9:37   ` Geert Uytterhoeven
2025-10-07  9:41     ` John Paul Adrian Glaubitz
2025-10-07 10:22       ` Geert Uytterhoeven
2025-10-07 11:23         ` Daniel Palmer
2025-10-07  9:23 ` [RFC PATCH 4/5] zorro: Add ids for Elbox Mediator 4000 Daniel Palmer
2025-10-07  9:23 ` [RFC PATCH 5/5] PCI: Add driver for Elbox Mediator 4000 Zorro->PCI bridge Daniel Palmer
2025-10-08 10:35   ` Ilpo Järvinen

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=20251007092313.755856-1-daniel@thingy.jp \
    --to=daniel@thingy.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-pci@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).