--pgp-sign-Multipart_Tue_Dec__6_05:43:06_2005-1
Content-Type: text/plain; charset=US-ASCII


> It seems to perform the basic functions (audio is emitted via amarok, xmms),
> however many applications, and all mixers I've tested don't seem to understand how
> to interact with it.  From mixerctl -a I get classes I can't immediately understand
> (snippet):

> Is it the driver's responsiblity to name the mixer classes in
> human readable form (as in the eap driver).
> 
> Or is it a software design issue; apps and mixers are looking
> for hard coded "inputs.dac" instead of reading/asking the
> driver for available classes?

The names "inputs" and "dac" are defined in sys/audioio.h, and
the driver is responsible to name mixer items in such standard
names, I think.

Unfortunately, HD Audio Codec specification is too flexible to
know automatically what node is the most suitable for
"inputs.dac".  So azalia(4) produces such unreadable mixer
names.  Azalia(4) in -current has capability to have
codec-specific code (sys/dev/pci/azalia_codec.c) and we should
add code to define "inputs.dac" for every codec.

-- 
TAMURA Kent <kent_2005 at hauN.org> <kent at NetBSD.org>

--pgp-sign-Multipart_Tue_Dec__6_05:43:06_2005-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iQEVAwUAQ5SmXn7t9398iwLqAQLK/wf/UtVS4oOR+MMRFR0NgkPRVhofDOFumDTO
1psmZIyC1mN4yfmxArEmqwVYUn8lTJ/RKc4AZaJd48TJVE3WWHTw45ubwCBC5IwY
4ZL2IKzX1DntPYasvFIjW+w+Qx0fUsApeacNpOjLdGz4Da867J/1qUUPXFcsSJQv
kq1yRNHn1s3a3o0Zd94Be1VChVw8wbOgDpcDektJ2wPFaI7qwj6nHWVIqHiQA9tE
F446Vz77nYar6dHeWoHRZlbR4vBujO+ztZV6ztd4mBRyDT2pXtTyvnTs2X7mGuwr
UJex2wuUBz/tSnTSzOvAS20OUeHqasvN18ey9ScTPsNhyTR1y2RqgA==
=+dNz
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Tue_Dec__6_05:43:06_2005-1--