From: vlse <vlse@veera.biz>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] Would there be virtio-audio spec in future for clean audio interface
Date: Tue, 26 Mar 2019 06:18:01 +0530 [thread overview]
Message-ID: <20190326004759.GD1872@localhost> (raw)
In-Reply-To: <60d7d47b-7ece-fe13-1784-831394807018@redhat.com>
On Mon, Mar 25, 2019 at 02:13:51PM +0100, Paolo Bonzini wrote:
> On 24/03/19 05:51, vlse wrote:
> > Would there be virtio-audio spec in future for clean audio interface?
> >
> > Projectacrn.github.io provides one virtio-audio interface for automotive sytems.
>
> That's interesting to know. It would probably be up to projectacrn to
> submit virtio-audio to the committee, or at least reserve the device
> number. Do you have a contact at projectacrn that can help with this?
>
> Thanks,
>
> Paolo
Hi,
No I don't have a contact with Project ACRN.
ACRN is a Linux Foundation Project. Initially it was by Intel.
It is a hypervisor for embedded devices.
Website is https://projectacrn.org/.
Their supported virtio-audio details:
Vendor ID: 0x8086
Device ID: 0x8603
Subvendor ID: 0x8086
Subdevice ID: 0xFFFD
Another implementation from another developer from Intel.
Website: https://patchwork.freedesktop.org/patch/174013/
Author: Luo Xionghu <xionghu.luo@intel.com>
Comments by Author: this patch only add audio device pci registration.
need add audio part to call audio Backend driver later.
Regards,
Veera
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2019-03-26 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190324043339.GA1884@localhost>
2019-03-24 4:51 ` [virtio-dev] Would there be virtio-audio spec in future for clean audio interface vlse
2019-03-25 13:13 ` Paolo Bonzini
2019-03-26 0:48 ` vlse [this message]
2019-03-26 9:38 ` Paolo Bonzini
2019-03-26 19:51 ` Tian, Kevin
2019-03-26 12:19 ` Jens Freimann
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=20190326004759.GD1872@localhost \
--to=vlse@veera.biz \
--cc=pbonzini@redhat.com \
--cc=virtio-dev@lists.oasis-open.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.