From: BALATON Zoltan <balaton@eik.bme.hu>
To: Sebastian Bauer <mail@sebastianbauer.info>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-ppc <qemu-ppc@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] sam460ex: Fix PCI interrupt connections
Date: Tue, 31 Jul 2018 13:24:41 +0200 (CEST) [thread overview]
Message-ID: <alpine.BSF.2.21.1807311320150.86593@zero.eik.bme.hu> (raw)
In-Reply-To: <dfd55d04ca9cd76ab22bfad5617ef388@sebastianbauer.info>
On Tue, 31 Jul 2018, Sebastian Bauer wrote:
> Am 2018-07-31 11:50, schrieb BALATON Zoltan:
>> On Tue, 31 Jul 2018, Sebastian Bauer wrote:
>>> There is also the possibility to make the special (num-irqs == 1) the
>>> common case, as the Sam460ex platform is the only user of this bus so far
>>> (and probably stays the only one). I'm not sure if it is worth all the
>>> hassle.
>>
>> I'd vote for this as I've said before. This seems to be the simplest
>> solution so just change ppc440_pcix to have one irq instead of 4.
>
> I now think so too, as, when devising my initial patch, I was not aware of
> the fact that this bus emulation was only created for the SAM.
>
>>> Let me know how to proceed.
>> Will you send an updated patch or should I take and modify your latest
>> one to help with this?
>
> I don't care so much about the how, but I would appreciate it, if the bug can
> be fixed, so that further PCI cards can be used without too much hassle
> (e.g., network cards). David seemed to be OK with my 2nd patch after I rebase
> it if I understood it correctly. My plan is to do this. But I'll also submit
> another alternative (shorter) patch that tailors the bus to the SAM only.
I've sent the shorter version as I think would be the easiest fix, please
check if this is acceptable which may save you some work on updating your
more complex patch which I think might not be needed at this point until
something is found to need more interrupts in the ppc440_pcix model.
I've checked that this improves sound with ES1370, haven't checked with
pci-ohci so you could verify that.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2018-07-31 11:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 4:39 [Qemu-devel] [PATCH] sam460ex: Fix PCI interrupt connections Sebastian Bauer
2018-07-30 4:49 ` David Gibson
2018-07-30 11:06 ` BALATON Zoltan
2018-07-30 12:04 ` Sebastian Bauer
2018-07-30 22:37 ` BALATON Zoltan
2018-07-30 23:00 ` Peter Maydell
2018-07-30 23:31 ` BALATON Zoltan
2018-07-31 0:18 ` David Gibson
2018-07-31 4:57 ` Sebastian Bauer
2018-07-31 6:06 ` David Gibson
2018-07-31 9:50 ` BALATON Zoltan
2018-07-31 10:32 ` Sebastian Bauer
2018-07-31 11:24 ` BALATON Zoltan [this message]
2018-07-30 22:47 ` Peter Maydell
2018-07-30 23:00 ` BALATON Zoltan
2018-07-30 23:15 ` Peter Maydell
2018-07-31 5:09 ` Sebastian Bauer
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=alpine.BSF.2.21.1807311320150.86593@zero.eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=david@gibson.dropbear.id.au \
--cc=mail@sebastianbauer.info \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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).