* BLOCK_TRANSFER flag in snd_pcm_hardware_t structure
@ 2003-02-19 17:06 Marc Titinger
2003-02-19 21:48 ` Jaroslav Kysela
2003-02-20 9:18 ` Takashi Iwai
0 siblings, 2 replies; 3+ messages in thread
From: Marc Titinger @ 2003-02-19 17:06 UTC (permalink / raw)
To: alsa-devel
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 ?
is this flag linked to the values of .period_bytes_min/max or .fifo_size ?
is this related to the hw_ptr granularity ?
tx
Marc.
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: BLOCK_TRANSFER flag in snd_pcm_hardware_t structure
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
1 sibling, 0 replies; 3+ messages in thread
From: Jaroslav Kysela @ 2003-02-19 21:48 UTC (permalink / raw)
To: Marc Titinger; +Cc: alsa-devel@lists.sourceforge.net
On Wed, 19 Feb 2003, 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 ?
> is this flag linked to the values of .period_bytes_min/max or .fifo_size ?
> is this related to the hw_ptr granularity ?
It's not related to anything which application can determine. Please,
don't rely so much on this flag. It is not well defined.
Jaroslav
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: BLOCK_TRANSFER flag in snd_pcm_hardware_t structure
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
1 sibling, 0 replies; 3+ messages in thread
From: Takashi Iwai @ 2003-02-20 9:18 UTC (permalink / raw)
To: Marc Titinger; +Cc: alsa-devel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-02-20 9:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.