OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [virtio-dev] Request for a new device number for a virtio-audio device.

Hi Marco,

On 11.05.19 22:49, Marco Martinelli - 13Byte srl wrote:
> Wow, it seems like you guys from opensinergy beat me on time. Nice job,
> congratulations!
Thanks a lot, I think out main problem was that we kept it under the
covers for so long.
> Your work is way ahead of mine, so much that I'm thinking of stepping
> aside and letting you do the specifications, while experimenting on my
> code privately just for the fun of it.
> Just a couple of questions.
> You mentioned that the PoC was tested on Linux and Windows 10. I presume
> these are the guest OSs.
For us, Linux is the primary guest OS at the moment.
> On the host side are you working on qemu or another hypervisor?
> Besides contributing to the specifications, will you open source the
> actual implementation?
The host side is another hypervisor.
> From your website I see you work in the automotive business. Will your
> implementation be automotive oriented or general purpose?
> My idea was to support the general public and in particular the gamers
> and the musicians with my project. I want to be sure that these
> categories will be supported.
Well, virtio is general purpose and so should all devices, even if we
use it in automotive contexts. TBH, automotive requirements aren't that
different from gaming or music production. You will often have very
strict latency requirements and need support for multiple channels
(coherent and non-coherent). So I think the overlap is huge.

But, as a matter of fact, I don't think Anton and I know exactly what
the general public is interested in so, your help would be very
appreciated here.

> The reason I'm asking these questions is to see if it makes sense for me
> to keep working on this project, perhaps to implement the specifications
> proposed by you, or if you're already taking care of everything I was
> interested in implementing.

It definitely makes sense for you to keep working on this, I believe
that we might not have the time at the moment to work on a full qemu
implementation and having an independent implementation of the device
side would be pretty awesome.

We plan to send patches for the device driver in Linux in the near
future and we might even be able to share the windows one (Anton should




Please mind our privacy notice<https://www.opensynergy.com/datenschutzerklaerung/privacy-notice-for-business-partners-pursuant-to-article-13-of-the-general-data-protection-regulation-gdpr/> pursuant to Art. 13 GDPR. // Unsere Hinweise zum Datenschutz gem. Art. 13 DSGVO finden Sie hier.<https://www.opensynergy.com/de/datenschutzerklaerung/datenschutzhinweise-fuer-geschaeftspartner-gem-art-13-dsgvo/>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]