From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: BLOCK_TRANSFER flag in snd_pcm_hardware_t structure Date: Thu, 20 Feb 2003 10:18:34 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <08F1D234AF91E540BC1F43889E2A6AA70AEC08@digiexch.digigram.com> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <08F1D234AF91E540BC1F43889E2A6AA70AEC08@digiexch.digigram.com> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Marc Titinger Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Wed, 19 Feb 2003 18:06:22 +0100, Marc Titinger wrote: > > Hi All, > > I can't figure out from the code what are the implications of having > the flag SNDRV_PCM_INFO_BLOCK_TRANSFER set in a > snd_pcm_hardware_t.info field ? this is an inherited flag from the older version, and plays no big role now. it's still checked in the OSS emulation code, though. > is this flag linked to the values of .period_bytes_min/max or .fifo_size ? no. > is this related to the hw_ptr granularity ? no. hw_ptr granularity is defined only by period_bytes_min (and additional constraints if any). Takashi ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge