Status of VIA Envy24 audio controller

[Konstantin Dimitrov]

i think "Audiophile 192" is Envy24HT-based (chip is marked ICE1724 or
VT1724), for the moment only Envy24-based cards (chip is marked ICE1712 or
VT1712) can be supported. Envy24HT and Envy24 are very similar, but have
several different registers and Envy24HT hasn't hardware mixer, so the
driver should be completely rewritten to support Envy24HT. i am planning to
do that, because i have "Terratec Aureon 7.1 Space", which is also
Envy24HT-based and when find free time for that i will start working on
implementing Envy24HT support.

for making EEPROM dump, you can use very small newbus module that i made
(before "make" ENVY24_PCI_ID in xkodi.h should be changed to correct value:
0x1712 for Envy24, 0x1724 for Envy24HT, etc.):

 http://xkodi.svobodno.com/xkodi/xkodi.h
http://xkodi.svobodno.com/xkodi/xkodi.c
 http://xkodi.svobodno.com/xkodi/Makefile

copy xkodi.h and xkodi.c to /usr/src/sys/dev/sound/pci/ and Makefile for
example to /usr/src/sys/modules/sound/driver/xkodi/ (in case you are
wondering "xkodi" is my nickname) and after make and kldload ./snd_xkodi.ko
you should see output to the console similar to:

xkodi0: <ENVY24> port
0xd500-0xd53f,0xd400-0xd40f,0xd300-0xd30f,0xd200-0xd21f irq 18 at device
10.0 on pci1
xkodi0: E2PROM DUMP:
    | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C OD 0E 0F
----+-------------------------------------------------
 00 | 11 38 15 3b 1c 01 2f 80 f0 03 c0 ff 7f 00 00 00
 01 | 00 00 00 44 03 03 03 00 03 03 03 00 ff ff ff ff


On 6/14/06, Damian Gerow <dgerow at afflictions.org> wrote:
>
> Thus spake Konstantin Dimitrov (kosio.dimitrov at gmail.com) [13/06/06
> 12:04]:
> : we also have EEPROM dumps of "Terratec DMX 6fire" and "M-Audio
> Audiophile
> : 2496" here:
> :
> : http://xkodi.svobodno.com/envy24/new/6fire.e2prom.dump
> : http://xkodi.svobodno.com/envy24/new/ap2496.e2prom.dump
>
> I have an Audiophile 192 that I'm *keenly* interested in getting
> functional.
> It's fairly different from the Terratec and the 2496 (both models
> mentioned), and I haven't had the time to dig through spec sheets.  The
> two
> attempts I made at getting the driver going resulted in a system panic.
>
> How might I go about grabbing an eeprom dump to help with development?
>