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 4/5] zorro: Add ids for Elbox Mediator 4000
Date: Tue, 7 Oct 2025 18:23:12 +0900 [thread overview]
Message-ID: <20251007092313.755856-5-daniel@thingy.jp> (raw)
In-Reply-To: <20251007092313.755856-1-daniel@thingy.jp>
Add the two ids for the Elbox Mediator 4000.
There are two because it presents as two boards:
- One that contains the control registers, PCI config + io space
- Another that contains a window that contains the PCI memory space
Signed-off-by: Daniel Palmer <daniel@thingy.jp>
---
drivers/zorro/zorro.ids | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/zorro/zorro.ids b/drivers/zorro/zorro.ids
index 119abea8c6cb..fda1db905412 100644
--- a/drivers/zorro/zorro.ids
+++ b/drivers/zorro/zorro.ids
@@ -369,6 +369,8 @@
1900 FastATA 4000 [IDE Interface]
1d00 FastATA 4000 [IDE Interface]
1e00 FastATA ZIV [IDE Interface]
+ 2100 Mediator 4000 (Control) [PCI bridge]
+ a100 Mediator 4000 (Window) [PCI bridge]
0a00 Harms Professional
1000 030 Plus [Accelerator]
d000 3500 Professional [Accelerator and RAM Expansion]
--
2.51.0
next prev parent 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 [RFC PATCH 0/5] PCI on the Amiga 4000 Daniel Palmer
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 ` Daniel Palmer [this message]
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-5-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).