From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Xen PV audio XenStore Date: Tue, 5 Jul 2011 10:54:57 -0400 Message-ID: <20110705145457.GC13548@dumpdata.com> References: <1309867328.634.116.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1309867328.634.116.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , George Boutsioukis List-Id: xen-devel@lists.xenproject.org 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//device/audio//event-channel > > /local/domain//device/audio//ring-ref > > /local/domain//device/audio//format > > /local/domain//device/audio//rate > > /local/domain//device/audio//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?