Paul Davis wrote:
>
> it *IS* done in the drivers. what makes you think i was talking about
> user-space?
OK, I misunderstood something.
> but the device drivers do not block interrupts while sync-starting
> multiple devices. perhaps they should. its rather ugly.
It depends how long it takes. If it falls right through the initialization
without any wait-loops I think it would be ok to disable interrupts.
There are few nasty NIC drivers that disable interrupts for too long time
and thus causing FIFO buffer overflows (Intel's e100 driver for example).
> its not that simple. you have to make sure that the driver software
> state is up-to-date when the h/w starts. you can't just issue out()'s
> and then pick up the pieces later. you have to make sure that the
> driver infrastructure is ready to start processing interrupts, etc.
Isn't this done in snd_pcm_prepare() (or something like that)? I think the
snd_pcm_start() should do just the very last piece to actually start the
device.
> snd_pcm_sync (card1, card2);
> snd_pcm_sync (card1, card3);
> snd_pcm_start (card1);
> ok?
Yep, OK. I'll look if I can make the latest beta work with my Delta1010.
- Jussi Laako
--
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B
Available at PGP keyservers
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
