At Wed, 22 Oct 2003 10:16:47 +0200, Tobias Peters wrote: > > >>Anyway, I think that we should leave the check as is for debugging > >>purposes (we should know that something is failing). > > > > > > sure, it's harmless message (as long as it comes from > > snd_pcm_update_hw_ptr()) but too annoying. there are too many > > sloppy hardwares... > > After printing the error message is printed, the function returns > immediately. Can you confirm that this does not have negative side > effects like dropped frames?
no, the hwptr must be updated correctly in snd_pcm_update_hw_ptr_interrupt() anyway. > Besides, the error messages popping up in the console interfere visually > with the text mode interface of the sound app that I use. this is likely because irq is not handled correctly when framebuffer is switched. the framebuffer is a bad source of irq blocking. Takashi ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
