From: Helge Deller <deller@kernel.org>
To: Peter Maydell <peter.maydell@linaro.org>,
Keith Monahan <keith@techtravels.org>,
BALATON Zoltan <balaton@eik.bme.hu>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Helge Deller <deller@gmx.de>
Subject: [PATCH 0/4] [RFC] scsi: New ncr53c710_v2 driver
Date: Fri, 6 Nov 2026 23:18:14 +0100 [thread overview]
Message-ID: <20261106221818.139086-1-deller@kernel.org> (raw)
From: Helge Deller <deller@gmx.de>
This patch series contains a replacement driver for the current ncr53c710
driver. The existing driver was written from scratch during the Google Summer
of Code 2025 program. It works okay with Linux, but fails badly when trying to
run any version of HP-UX or BSD.
Keith Monahan tried to fix the existing driver. But after some hacking it
became clear that starting fresh and using the lsi53c895a driver as base seems
more promising to get a correctly functional driver.
His patches to replace the existing driver [1] in-place were rejected because
the patches were too big (and changed too many not-related things inside one
patch) and thus a potential review seemed impossible (which I agree on).
Since the new driver is not fixing the old driver, but is actually a completely
new driver, trying to put together patches which replace the old driver step by
step is impossible. I gave it a shot, but failed badly.
As the maintainer of the PA-RISC emulation (which is actually the only user of
the ncr53c710 driver), I'm of course very much interested in having the new
functional driver instead of the old broken driver. The new driver works
reliable with Linux, HP-UX 9.05, HP-UX 10.20 and NetBSD, which is a big step
forward.
My proposed solution to this issue in this patch series is:
- in patch #2: add the new driver (v2) in a new source file: ncr53c710_v2.c
- in patch #3: wire up the new driver instead of the old driver
- in patch #4: remove the code of the old driver (ncr53c710.c)
Usually I'd prefer an evolutionary way to the new driver as well, but if you
check the code yourself you will see this will not be possible.
That said, I would be happy if my proposal here would be accepted.
Thanks!
Helge
[1] https://lists.nongnu.org/archive/html/qemu-devel/2026-07/msg00263.html
Helge Deller (4):
target/hppa: drop dependency on ncr53c710.h
ncr53c710_v2: add new NCR53C710 chipset driver
lasi_ncr710: Wire up the new ncr53c710_v2 driver in LASI
hw/scsi: Drop old ncr53c710 v1 driver
hw/hppa/machine.c | 1 -
hw/scsi/lasi_ncr710.c | 119 +-
hw/scsi/lasi_ncr710.h | 30 +-
hw/scsi/meson.build | 2 +-
hw/scsi/ncr53c710.c | 2473 ----------------------------------------
hw/scsi/ncr53c710.h | 246 ----
hw/scsi/ncr53c710_v2.c | 1969 ++++++++++++++++++++++++++++++++
hw/scsi/ncr53c710_v2.h | 183 +++
hw/scsi/trace-events | 36 +
9 files changed, 2240 insertions(+), 2819 deletions(-)
delete mode 100644 hw/scsi/ncr53c710.c
delete mode 100644 hw/scsi/ncr53c710.h
create mode 100644 hw/scsi/ncr53c710_v2.c
create mode 100644 hw/scsi/ncr53c710_v2.h
--
2.54.0
next reply other threads:[~2026-11-06 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 22:18 Helge Deller [this message]
2026-11-06 22:18 ` [PATCH 1/4] target/hppa: drop dependency on ncr53c710.h Helge Deller
2026-11-06 22:18 ` [PATCH 2/4] ncr53c710_v2: add new NCR53C710 chipset driver Helge Deller
2026-11-08 11:43 ` BALATON Zoltan
2026-11-08 12:49 ` Helge Deller
2026-11-08 13:01 ` BALATON Zoltan
2026-11-11 3:19 ` Keith Monahan
2026-11-11 13:26 ` BALATON Zoltan
2026-11-06 22:18 ` [PATCH 3/4] lasi_ncr710: Wire up the new ncr53c710_v2 driver in LASI Helge Deller
2026-11-06 22:18 ` [PATCH 4/4] hw/scsi: Drop old ncr53c710 v1 driver Helge Deller
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=20261106221818.139086-1-deller@kernel.org \
--to=deller@kernel.org \
--cc=balaton@eik.bme.hu \
--cc=deller@gmx.de \
--cc=keith@techtravels.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.