--lteA1dqeVaWQ9QQl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 13, 2006 at 06:21:12PM +0100, Antoine Reilles wrote:
> On Mon, Feb 13, 2006 at 09:18:56AM -0800, Chuck Silvers wrote:
> > On Fri, Feb 10, 2006 at 10:47:26PM +0100, Antoine Reilles wrote:
> > > audio at snapper0 not configured
> >=20
> > this is a problem.  the common audio code isn't figuring out that
> > snapper is an audio device somehow.
> sorry, my mail wasn't clear at all.
> I had this=20
> audio at snapper0 not configured
> because in the GENERIC config, audio at snapper is commented (macallan
> fixd this). I just hadn't checked for that, since snapper itself was
> uncommented, it was natural to think audio at snapper was there.
> I changed that to
> audio at audiobus, and it went fine
>=20
> Now i get in dmesg:
> audio0 at snapper0: full duplex
>=20
> but still no sound ;-(

I built a kernel with SNAPPER_DEBUG

When i try to play something, i get

I2SSetDataWordSizeReg 0x02020202 -> 0x02000200
I2SSetSerialFormatReg 0x0 -> 0x3190000
I2SSetDataWordSizeReg 0x02020202 -> 0x02000200
I2SSetSerialFormatReg 0x0 -> 0x81190000
I2SSetDataWordSizeReg 0x02020202 -> 0x02000200
I2SSetSerialFormatReg 0x0 -> 0x3190000
I2SSetDataWordSizeReg 0x02020202 -> 0x02000200
I2SSetSerialFormatReg 0x0 -> 0x81190000
I2SSetDataWordSizeReg 0x02020202 -> 0x02000200
I2SSetSerialFormatReg 0x0 -> 0x3190000
I2SSetDataWordSizeReg 0x02020202 -> 0x02000200
I2SSetSerialFormatReg 0x0 -> 0x41190000
trigger_output 0xd049c000 0xd04ac000 0x2000

in dmesg, and it looks like the player application is blocked
in the write operation
 1106 tonio     10    0  2328K 1576K aud_wr     0:00  0.00%  0.00% mpg321

--=20
antoine

--lteA1dqeVaWQ9QQl
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFD8QEl4VqmoGDE/mwRAqvuAJ9UokNLRoQ7PT11aytUfr8RmQyjQgCfRHPi
z3XlUjXdHf9A4nn90e2jnzc=
=iVrp
-----END PGP SIGNATURE-----

--lteA1dqeVaWQ9QQl--