> Look at the physical addresses. They're spaced by 4KB, but the periods
> are 11KB long and 11026*3<44100 !! You can imagine how beatiful sound I
> get... What am I missing ?
Ehm, I found the problem, ignore my previous msg.
Bye.
---
This
On mar, 2003-03-18 at 13:32, Takashi Iwai wrote:
> also, don't forget to unlock the spinlock during calling
> snd_pcm_period_elapsed() if a single lock is used for callbacks.
Yes, I'm following the tutorial and it's clear about that.
Now I have another weird problem. This is a peice of my hw_para
At Mon, 17 Mar 2003 15:22:45 +0100 (CET),
Giuliano Pochini wrote:
>
>
> On 17-Mar-2003 Takashi Iwai wrote:
> > usually in the interrupt handler, you need to just send "ack" to the
> > middle layer by calling snd_pcm_period_elapsed(). then, the
> > middle-layer checks the current position by call
On 17-Mar-2003 Takashi Iwai wrote:
> usually in the interrupt handler, you need to just send "ack" to the
> middle layer by calling snd_pcm_period_elapsed(). then, the
> middle-layer checks the current position by calling pointer callback,
> and copy/send/set-silence in the necessary area.
I did
At Mon, 17 Mar 2003 10:17:04 +0100 (CET),
Giuliano Pochini wrote:
>
>
> > When an interrupt arrives and I call snd_pcm_period_elapsed(), what
> > function gets from alsa middle layer the new block to play and sets up
> > the hardware ?
>
> Ok, nobody answered, perhaps my question was too stupid
> When an interrupt arrives and I call snd_pcm_period_elapsed(), what
> function gets from alsa middle layer the new block to play and sets up
> the hardware ?
Ok, nobody answered, perhaps my question was too stupid :))
I still haven't found in the docs how can I get from ALSA the
address of the
When an interrupt arrives and I call snd_pcm_period_elapsed(), what
function gets from alsa middle layer the new block to play and sets up
the hardware ?
Bye.
---
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking
