[alsa-devel] Alsa OSS - who is maintaining it?
Stefan de Konink
skinkie at xs4all.nl
Wed Apr 4 23:43:44 CEST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Johannes Berg wrote:
> On Wed, 2007-04-04 at 20:42 +0200, Stefan de Konink wrote:
>
>>> /*
>>> * For input, we need to do a graceful stop; if we abort
>>> * the DMA, we end up with leftover bytes that corrupt
>>> * the next recording. To do this we set the S0 status
>>> * bit and wait for the DMA controller to stop. Each
>>> * command has a branch condition to
>>> * make it branch to a stop command if S0 is set.
>>> * On input we also need to wait for the S7 bit to be
>>> * set before turning off the DMA controller.
>>> * In fact we do the graceful stop for output as well.
>>> */
>> Check, I have that.
>
> Hm. Then I don't know what could be causing this. Does it happen all the
> time or just intermittently?
With every OSS app out there... but native alsa works fine.
Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGFBwQYH1+F2Rqwn0RCi2dAJ9Vlel3cz0PAUMvgYi7L2Nd3XCc9wCeJG9H
NT+AsNRL91Dm1y9Dlch75PU=
=xxif
-----END PGP SIGNATURE-----
More information about the Alsa-devel
mailing list