WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen PV audio XenStore

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen PV audio XenStore
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 5 Jul 2011 10:54:57 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, George Boutsioukis <gboutsioukis@xxxxxxxxx>
Delivery-date: Tue, 05 Jul 2011 07:55:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1309867328.634.116.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CANnAuxArNOO_1qAaDfMxN9CDEgvHxhk0BAhxzUf7fZdvs4t7UQ@xxxxxxxxxxxxxx> <1309867328.634.116.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Tue, Jul 05, 2011 at 01:02:08PM +0100, Ian Campbell wrote:
> On Mon, 2011-07-04 at 23:16 +0100, George Boutsioukis wrote:
> > Hello everyone, as some of you may remember there is a GSoC project
> > this year to implement a paravirtualized audio driver and I am the
> > student undertaking this effort.
> > 
> > As the rest of the PV audio drivers, my frontend uses XenStore to pass
> > the event channel & grant reference to the backend, along with a few
> > configuration data. Although the driver is far from usable, the
> > XenStore layout is not going to change much in the future, so I think
> > it would be useful to describe it to the community.
> > 
> > First of all, although the frontend is implemented in userspace, I
> > tried to follow the scheme used by the rest of the PV drivers. This
> > looks something like:
> > 
> > /local/domain/<domID>/device/audio/<devID>/event-channel
> > /local/domain/<domID>/device/audio/<devID>/ring-ref
> > /local/domain/<domID>/device/audio/<devID>/format
> > /local/domain/<domID>/device/audio/<devID>/rate
> > /local/domain/<domID>/device/audio/<devID>/channels

And "format" is...? string? What does it look like?
> > 
> > where devID is a unique device ID for the guest system.

Could you provide an example of what this layout looks like for
stereo microphone (each channel is 8bit-unsigned, 44Khz) and
5.1 channel output with 48Khz of ulaw-16bit signed?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>