From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [PATCH] Kernel crash Date: Fri, 24 Sep 2004 15:30:59 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <20040911210212.317d930b.pochini@shiny.it> <20040913220729.466531ce.pochini@shiny.it> <20040915195008.33713acb.pochini@shiny.it> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Jaroslav Kysela Cc: Giuliano Pochini , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Thu, 23 Sep 2004 09:43:39 +0200 (CEST), Jaroslav wrote: > > On Wed, 22 Sep 2004, Takashi Iwai wrote: > > > OTOH, when you link streams but feed/read data separately for each > > stream, the clock difference doesn't matter. Each stream may have > > even different periods, buffer sizes, whatever. > > > > So, in the first case, handling xrun/drain/drop in sync of all linked > > streams makes sense. But what about the second case...? > > > > Well, the link can be removed dynamically. So, in theory, we can > > propose like the following: > > > > - Start, drain, drop and xrun of linked streams are operated to all > > streams by a single call. Especially, drain assures that the all > > streams get sync'ed. > > > > - When one wants to operate drain and drop separately, explicitly > > unlink streams after the sync'ed start. > > This proposal seems reasonable. Shall I apply my patch to CVS, or would you like to audit it more? thanks, Takashi ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php