From: Takashi Iwai <tiwai@suse.de>
To: Marc Titinger <titinger@digigram.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: BLOCK_TRANSFER flag in snd_pcm_hardware_t structure
Date: Thu, 20 Feb 2003 10:18:34 +0100 [thread overview]
Message-ID: <s5hu1ezfgyd.wl@alsa2.suse.de> (raw)
In-Reply-To: <08F1D234AF91E540BC1F43889E2A6AA70AEC08@digiexch.digigram.com>
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
prev parent reply other threads:[~2003-02-20 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 17:06 BLOCK_TRANSFER flag in snd_pcm_hardware_t structure Marc Titinger
2003-02-19 21:48 ` Jaroslav Kysela
2003-02-20 9:18 ` Takashi Iwai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hu1ezfgyd.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=titinger@digigram.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox