From: "Leif Lindholm" <leif@nuviainc.com>
To: Michael Brown <mcb30@ipxe.org>
Cc: Laszlo Ersek <lersek@redhat.com>,
Ethin Probst <harlydavidsen@gmail.com>,
devel@edk2.groups.io
Subject: Re: [edk2-devel] VirtIO sound device in qemu?
Date: Wed, 9 Jun 2021 13:48:22 +0100 [thread overview]
Message-ID: <20210609124822.6ohlxxuzk7izej57@leviathan> (raw)
In-Reply-To: <883acfee-86e1-6924-ce0f-ae65ce449fa0@ipxe.org>
On Wed, Jun 09, 2021 at 13:25:16 +0100, Michael Brown wrote:
> On 09/06/2021 11:57, Laszlo Ersek wrote:
> > I'm uneducated about the "deliverables" in GSoC, but in general I'd
> > suggest narrowing down the scope as much as possible. I don't know how
> > hard it is to program USB audio, but if QEMU provides a good device
> > model for that, out of the box, I would recommend basing the edk2 work
> > on that device.
>
> QEMU also has good support for passing through a real USB device, which
> might be useful if you ever suspect that the QEMU device implementation is
> behaving incorrectly.
I have used the USB passthrough in anger, and sometimes it has been
flawless, but other times it has been flaky.
So, yes - it is worth cross-checking real and emulated hw when running
into unexpected issues, but the passed-through hw is not automatically
more reliable.
/
Leif
> (This is not implausible: I still have several bugfixes for the QEMU USB
> network device emulation sitting in an out-of-tree branch.)
>
> Michael
next prev parent reply other threads:[~2021-06-09 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 4:41 VirtIO sound device in qemu? Ethin Probst
2021-06-07 11:40 ` [edk2-devel] " Michael Brown
2021-06-07 15:16 ` Laszlo Ersek
2021-06-07 18:54 ` Ethin Probst
2021-06-07 21:33 ` Leif Lindholm
2021-06-08 18:52 ` Ethin Probst
2021-06-08 20:25 ` Leif Lindholm
2021-06-08 23:29 ` Rafael Machado
2021-06-09 10:57 ` Laszlo Ersek
2021-06-09 12:25 ` Michael Brown
2021-06-09 12:48 ` Leif Lindholm [this message]
2021-06-09 13:43 ` Ethin Probst
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-list 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=20210609124822.6ohlxxuzk7izej57@leviathan \
--to=devel@edk2.groups.io \
/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