From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: "Ughreja, Rakesh A" <rakesh.a.ughreja@intel.com>
Cc: 'Takashi Iwai' <tiwai@suse.de>,
"'alsa-devel@alsa-project.org'" <alsa-devel@alsa-project.org>
Subject: Re: Para-virtualized audio drivers
Date: Wed, 19 Oct 2016 11:27:58 +0100 [thread overview]
Message-ID: <1476872878.11707.24.camel@loki> (raw)
In-Reply-To: <85DFEED57DC57344B2483EF7BF8CB60552C5B457@BGSMSX104.gar.corp.intel.com>
On Mon, 2016-10-17 at 03:01 +0000, Ughreja, Rakesh A wrote:
> Hi Takashi and all,
>
> I have some need to develop para virtualized audio drivers which can
> work with XEN hypervisor.
>
> I see some attempt was made in the past.
> https://lists.xen.org/archives/html/xen-devel/2015-01/msg02125.html
>
> I see one more material but with no code.
> http://rd.springer.com/chapter/10.1007%2F978-94-007-2105-0_46
>
> I am thinking to develop pv-audio-frontend (running on Dom1) and
> pv-audio-backend (running on Dom0) drivers all at kernel level.
> Backend driver owns the hardware. Frontend driver communicates with
> backend driver using XENbus framework just like storage and network PV
> drivers.
>
> Before I start, I wanted to check if there is any other
> work that has been done which I can take as base ?
>
Fwiw, I've done something similar over 2 VMs for the audio DSP on
Baytrail. i.e. one VM is x86 Qemu/KVM running the host OS and kernel,
whilst the other VM is xtensa Qemu running the DSP firmware.
Details here :-
http://alsa-project.org/main/index.php/Firmware#Using_the_Qemu_DSP_emulator
Liam
next prev parent reply other threads:[~2016-10-19 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 3:01 Para-virtualized audio drivers Ughreja, Rakesh A
2016-10-19 10:27 ` Liam Girdwood [this message]
2016-10-20 15:26 ` Takashi Iwai
2016-10-20 17:02 ` Ughreja, Rakesh A
2016-10-20 18:09 ` Takashi Iwai
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=1476872878.11707.24.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=rakesh.a.ughreja@intel.com \
--cc=tiwai@suse.de \
/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