From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
Bernhard Beschow <shentey@gmail.com>,
philmd@redhat.com
Subject: Re: [PATCH 3/5] hw/ppc/pegasos2: Fix PCI interrupt routing
Date: Sat, 25 Feb 2023 20:34:06 +0100 [thread overview]
Message-ID: <fff5cea4-43e6-60ff-4266-c0753d1dfd38@linaro.org> (raw)
In-Reply-To: <c046d77c20875c8cd8bfdc79b4619a98ffd0bf33.1677004415.git.balaton@eik.bme.hu>
On 21/2/23 19:44, BALATON Zoltan wrote:
> According to the PegasosII schematics the PCI interrupt lines are
> connected to both the gpp pins of the Mv64361 north bridge and the
> PINT pins of the VT8231 south bridge so guests can get interrupts from
> either of these. So far we only had the MV64361 connections which
> worked for on board devices but for additional PCI devices (such as
> network or sound card added with -device) guest OSes expect interrupt
> from the ISA IRQ 9 where the firmware routes these PCI interrupts in
> VT8231 ISA bridge. After the previous patches we can now model this
> and also remove the board specific connection from mv64361. Also
> configure routing of these lines when using Virtual Open Firmware to
> match board firmware for guests that expect this.
>
> This fixes PCI interrupts on pegasos2 under Linux, MorphOS and AmigaOS.
>
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> ---
> hw/pci-host/mv64361.c | 4 ----
> hw/ppc/pegasos2.c | 26 +++++++++++++++++++++++++-
> 2 files changed, 25 insertions(+), 5 deletions(-)
> +static void pegasos2_pci_irq(void *opaque, int n, int level)
> +{
> + Pegasos2MachineState *pm = opaque;
> +
> + /* PCI interrupt lines are connected to both MV64361 and VT8231 */
> + qemu_set_irq(pm->mv_pirq[n], level);
> + qemu_set_irq(pm->via_pirq[n], level);
> +}
See TYPE_SPLIT_IRQ.
next prev parent reply other threads:[~2023-02-25 19:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 18:44 [PATCH 0/5] Pegasos2 fixes and audio output support BALATON Zoltan
2023-02-21 18:44 ` [PATCH 1/5] hw/isa/vt82c686: Implement interrupt routing in via_isa_set_irq BALATON Zoltan
2023-02-21 18:44 ` [PATCH 2/5] hw/isa/vt82c686: Implement PIRQ pins BALATON Zoltan
2023-02-21 18:44 ` [PATCH 3/5] hw/ppc/pegasos2: Fix PCI interrupt routing BALATON Zoltan
2023-02-24 17:04 ` Daniel Henrique Barboza
2023-02-25 19:34 ` Philippe Mathieu-Daudé [this message]
2023-02-25 20:19 ` BALATON Zoltan
2023-02-26 22:22 ` BALATON Zoltan
2023-02-21 18:44 ` [PATCH 4/5] hw/audio/ac97: Split off some definitions to a header BALATON Zoltan
2023-02-25 19:35 ` Philippe Mathieu-Daudé
2023-02-26 22:17 ` BALATON Zoltan
2023-02-21 18:44 ` [PATCH 5/5] hw/audio/via-ac97: Basic implementation of audio playback BALATON Zoltan
2023-02-23 19:40 ` Volker Rümelin
2023-02-24 9:53 ` Bernhard Beschow
2023-02-24 12:26 ` BALATON Zoltan
2023-02-24 13:05 ` BALATON Zoltan
2023-02-24 17:14 ` Daniel Henrique Barboza
2023-02-24 21:08 ` BALATON Zoltan
2023-02-25 8:58 ` Daniel Henrique Barboza
2023-02-22 15:38 ` [PATCH 0/5] Pegasos2 fixes and audio output support Bernhard Beschow
2023-02-22 18:56 ` Bernhard Beschow
2023-02-22 19:25 ` BALATON Zoltan
2023-02-22 20:59 ` Bernhard Beschow
2023-02-22 21:12 ` BALATON Zoltan
2023-02-22 22:20 ` Bernhard Beschow
2023-02-22 23:00 ` BALATON Zoltan
2023-02-23 9:13 ` Bernhard Beschow
2023-02-23 12:33 ` BALATON Zoltan
2023-02-23 13:17 ` Bernhard Beschow
2023-02-23 14:23 ` BALATON Zoltan
2023-02-23 20:28 ` Bernhard Beschow
2023-03-01 13:49 ` Mark Cave-Ayland
2023-03-01 19:24 ` BALATON Zoltan
2023-03-01 20:53 ` Bernhard Beschow
2023-03-01 21:05 ` BALATON Zoltan
2023-03-01 13:42 ` Mark Cave-Ayland
2023-03-01 19:21 ` BALATON Zoltan
2023-02-22 22:23 ` BALATON Zoltan
2023-02-23 0:43 ` BALATON Zoltan
2023-03-01 13:47 ` Mark Cave-Ayland
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=fff5cea4-43e6-60ff-4266-c0753d1dfd38@linaro.org \
--to=philmd@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=danielhb413@gmail.com \
--cc=kraxel@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=shentey@gmail.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;
as well as URLs for NNTP newsgroup(s).