ok, i added more printk's in the trident driver to track exactly what the interrupt sequence is.
and what do you know ... if i add just one printk at the top, this doesn't stop things going wrong. if i add two printk's to tell me more about the nature of the interrupts, suddenly, everything works again. this stinks of a data race to me. with 0 or 1 interrupt printks - almost deterministic failure to wake up the capture stream reliably; add 1 more, and it works. is this likely to be a trident-specific issue? or can i assume that things look better on other hardware (i know it works right on the hammerfall) ? --p _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
