At Mon, 7 Jun 2004 12:43:01 +0200 (CEST), Jaroslav wrote: > > On Mon, 7 Jun 2004, Russell King wrote: > > > Actually, I disagree. It's an ALSA bug. The warning is created if > > the AACI close method is called while the DMA or IO is still running. > > If DMA is still running here, we've already freed the DMA buffer, so > > we're either reading from or writing to memory we don't own - which is > > a major bug. > > > > The question is therefore: why is ALSA trying to shut down and free a > > device which still has DMA running? To be more explicit, why didn't > > ALSA call the trigger callback with SNDRV_PCM_TRIGGER_STOP prior to > > calling the hw_free or close methods? > > The midlevel calls *drop() (which must stop the running stream) and then > ->hw_free and ->close callbacks. I've never seen this error, so I suspect > that something else is wrong.
i guess so, too. as you can see in the original post, the error returned from hw_params callback (sample not available), thus it doesn't call trigger(START) callback yet at all. unfurtunately i can't tell any more unless i read the driver code. where can i find the code? Takashi ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
