From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: pointer callback question Date: Fri, 13 Feb 2009 07:26:24 +0100 Message-ID: References: <49946175.5070008@klingt.org> <499462A5.2000705@klingt.org> <4994649A.8080005@klingt.org> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 3337C1037FB for ; Fri, 13 Feb 2009 07:26:25 +0100 (CET) In-Reply-To: <4994649A.8080005@klingt.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Tim Blechmann Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Thu, 12 Feb 2009 19:04:10 +0100, Tim Blechmann wrote: > > Takashi Iwai wrote: > > At Thu, 12 Feb 2009 18:55:49 +0100, > > Tim Blechmann wrote: > >>>> the brief log is (4 periods of 64 frames): > >>>> stream_pointer at 64 > >>>> stream_pointer at 128 > >>>> stream_pointer at 192 > >>>> stream_pointer at 256 > >>> This is invalid. The pointer callback must return 0 in this case. > >>> The value the pointer callback returns is between 0 and buffer_size-1. > >> sry, typo, 5 periods of 64 frames > > > > Then it must be OK. If the stream is stopped, it's likely by the > > buffer underrun detection or so... > > is there any way to compile alsa to get some debugging information about > that? Did you enable CONFIG_SND_DEBUG=y and others? Takashi