From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: "Bernhard Beschow" <shentey@gmail.com>,
"Volker Rümelin" <vr_qemu@t-online.de>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Gerd Hoffmann" <kraxel@redhat.com>,
philmd@linaro.org, "Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH 5/5] hw/audio/via-ac97: Basic implementation of audio playback
Date: Sat, 25 Feb 2023 05:58:11 -0300 [thread overview]
Message-ID: <c3e26f55-26c1-86ca-b3fd-b2237ae937b4@gmail.com> (raw)
In-Reply-To: <32aa39da-e6ec-4fcb-99fa-e1a09906decc@eik.bme.hu>
On 2/24/23 18:08, BALATON Zoltan wrote:
> On Fri, 24 Feb 2023, Daniel Henrique Barboza wrote:
>> On 2/24/23 10:05, BALATON Zoltan wrote:
>>> Just for some motivation, this is what we want to make possible for more people with QEMU 8.0: https://youtu.be/YY9RExl4VDI
>>
>> That's neat!
>>
>>>
>>> This would need at least my SM502 patches and fixing the IRQ routing in the VT8231 (this test was with my series for that, I'll ask testing Bernhard's version the same way once I get it and rebase my patches on it). AmigaOS can use ES1370 so the via-ac97 patches are not that important now but the other patches would be needed. I hope users won't have to wait until September to try this.
>>
>> If you're referring to "hw/display/sm501: Implement more 2D raster operations" then it's already
>> queued in ppc-next.
>
> That one and another I've sent yesterday that adds fallbacks for pixman routines.
>
>> In fact I believe you can re-send it with this series, with my r-b, and whoever
>> gets to send the PR can send everything at once.
>
> OK I'll collect all the patches in one series and submit it early next week. Hopefully we can test over the weekend and address any comments by the freeze.
Yes please.
>
>> If either Gerd of Phil wants to pick these up I have already acked the pegasos2 changes.
>>
>> If you want me to get this via qemu-ppc bear in mind that I need to send the PR March 7th
>> at the latest.
>
> I'm aware of that, although if we get more CI outage which stops pulls maybe we should consider 1-2 week extension, but I'm planning accordingly and if there won't be unexpected delays (e.g. new late reviews asking for extensive changes) this should be ready a week before the freeze. I think we can do one or two more versions/
It's no possible to predict this kind of unexpected delay, yes. But in the end the
maintainer is here to mediate these situations. If the patches have acks and the
maintainer considered it worth pushing, then this late review must be so good that
it convinces the maintainer to drop the patches from the PR (and from the release,
in this case).
It can happen, sure, but it's not a given. Specially considering that we have a good
code freeze window to fix any bugs that we might have left behind during the development
cycle.
Thanks,
Daniel
>
> Regards,
> BALATON Zoltan
next prev parent reply other threads:[~2023-02-25 8:59 UTC|newest]
Thread overview: 43+ 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é
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 20:20 [PATCH 0/5] VT82xx PCI " Bernhard Beschow
2023-02-23 20:20 ` [PATCH 5/5] hw/audio/via-ac97: Basic implementation of audio playback Bernhard Beschow
2023-03-01 14:25 ` Mark Cave-Ayland
2023-03-01 16:09 ` BALATON Zoltan
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=c3e26f55-26c1-86ca-b3fd-b2237ae937b4@gmail.com \
--to=danielhb413@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=shentey@gmail.com \
--cc=vr_qemu@t-online.de \
/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).