From: BALATON Zoltan <balaton@eik.bme.hu>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: USB-audio sound issues with qemu-system-ppc in Linux and Windows.
Date: Sat, 26 Oct 2019 11:38:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.BSF.2.21.99999.352.1910261123220.27453@zero.eik.bme.hu> (raw)
In-Reply-To: <CABLmASGCX07G7bOcTYZuqLDzoZ9eEyF9t61hKHhC343jxRtUdg@mail.gmail.com>
Hello,
On Sat, 26 Oct 2019, Howard Spoelstra wrote:
> I'd like to add to the previous report that similar issues are present in
> OSX (Sierra) builds of qemu-system-ppc.
I think the problem is not specific to host OS so instead of giving
debugging info for all hosts which would just confuse anyone trying to
reproduce it, it may be better to just concentrate on Linux (as that's
what most developers would have) and ignore Windows and OSX hosts for now.
It's probably also not specific to MacOS guests because I get similar
crackling sound on sam460ex with the ES1370 device with AmigaOS4 and can
reproduce the usb-audio shows up but does not make sound problem on
mac99,via=pmu with MorphOS so maybe either it's something with the sound
backend (like a buffer underflow in case of crackling that may be improved
by tweaking some parameters but I don't know what parameters are available
or how to set them) or maybe a problem with irqs (in case of no sound or
crashing MacOS guest but I don't know how to debug that either). Or I may
be completely wrong with my guesses so any advice from people knowing
sound and USB emulation in QEMU better is very welcome. (Also likely there
are more than one problem here so reporting them at once is also
confusing, these may need to be debugged separately.)
So to most likely get useful feedback you should find a simple way to
reproduce it with Linux host and guest and describe that in the shortest
way to make it easy for interested developers to reproduce it then also cc
your Gerd who is the audio and USB maintainer. Otherwise it's likely these
will get ignored because nobody can reproduce it who would able to attempt
debugging it.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2019-10-26 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 13:28 USB-audio sound issues with qemu-system-ppc in Linux and Windows Howard Spoelstra
2019-10-26 7:40 ` Howard Spoelstra
2019-10-26 9:38 ` BALATON Zoltan [this message]
2019-10-26 9:45 ` BALATON Zoltan
-- strict thread matches above, loose matches on Subject: below --
2019-10-25 6:36 [PULL v2 00/73] tcg plugins and testing updates Alex Bennée
2019-10-25 6:36 ` [PULL v2 46/73] target/alpha: fetch code with translator_ld Alex Bennée
2019-10-25 7:40 ` USB-audio sound issues with qemu-system-ppc in Linux and Windows Howard Spoelstra
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.99999.352.1910261123220.27453@zero.eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=hsp.cat7@gmail.com \
--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 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).