On Wed, Jul 22, 2020 at 08:55:02AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > IIUC, QEMU can expose multiple sound devices to the guest too.
> >
> > I think this means that we can have a M:N relationship between
> > a sound device, and an audio backend, not just 1:1.
>
> It's 1:N. Sound devices
Daniel P. Berrangé wrote:
> On Sat, Jul 18, 2020 at 04:31:16PM +0400, Roman Bogorodskiy wrote:
> > Extend device element to accept "soundDevice"
> > sub-element which allows to map guest sound device to host
> > sound device.
> >
> > Example
> >
> >
> >
> >
>
> IIUC, FreeBSD's
Hi,
> IIUC, QEMU can expose multiple sound devices to the guest too.
>
> I think this means that we can have a M:N relationship between
> a sound device, and an audio backend, not just 1:1.
It's 1:N. Sound devices have a single backend, but a backends can
service multiple sound devices.
>
On Sat, Jul 18, 2020 at 04:31:16PM +0400, Roman Bogorodskiy wrote:
> Extend device element to accept "soundDevice"
> sub-element which allows to map guest sound device to host
> sound device.
>
> Example
>
>
>
>
IIUC, FreeBSD's audio subsystem is the classic OSS API ?
>
> The
Extend device element to accept "soundDevice"
sub-element which allows to map guest sound device to host
sound device.
Example
The "playback" attribute points to the playback device,
and "recording" attribute points to the recording device.
Signed-off-by: Roman Bogorodskiy
---
