Subject: Intel 82801DB AC-97 Audio
To: None <tech-kern@netbsd.org>
From: Ian McIntosh <ianm@cat.co.za>
List: tech-kern
Date: 08/13/2003 11:31:52
This is a multi-part message in MIME format.
------=_NextPart_000_06E4_01C3618E.7DF2A490
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I think this is the correct forum for this, if not I apologise and ask =
to be directed
to the correct one.
I recently have tried to get the Intel 82801DB AC-97 Audio controller =
working
on netbsd 1.6.1. I found the the device was not picked up on boot up
and thus was not configured so I figured I would dig and see if I could =
get the=20
kernel to see the device. I noticed the product ID was in the pcidevs.h =
file
and thus tried to just add it to the src/sys/dev/pci/auich.c file to get =
audio=20
working. The result was that the device was found but then failed with=20
the message "auich_read_codec: codec is not ready" repeated. So I looked
in the -current for an update of the driver file. The version of auich.c =
I have is 1.17. I
found that version 1.18 in current (going back to Aug 2002) had support =
for my=20
audio device and so included it along with the corresponding auichreg.h =
and=20
recompiled my kernel. To get it to compile I needed to remove on or two =
product
ID's which weren't in my version of pcidevs.h.This worked fine and now =
I have audio.
I have two questions: Firstly I am concerned as to the impact of this =
''hack". I think it should
not really affect much else but would like the experts opinions.
Secondly I was wondering when the 1.6 branch of cvs will be updated to =
include the fix
for this audio device?
Thank you in advance
Ian
------=_NextPart_000_06E4_01C3618E.7DF2A490
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>I think this is the correct forum for =
this, if not=20
I apologise and ask to be directed</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>to the correct one.</FONT></DIV>
<DIV> </DIV></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I recently have tried to get the Intel =
82801DB=20
AC-97 Audio controller working</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>on netbsd 1.6.1. I found the the device =
was not=20
picked up on boot up</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and thus was not configured so I =
figured I would=20
dig and see if I could get the </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>kernel to see the device. I noticed the =
product ID=20
was in the pcidevs.h file</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and thus tried to just add it to the=20
src/sys/dev/pci/auich.c file to get audio </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>working. The result was that the device =
was found=20
but then failed with </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the message "auich_read_codec: codec is =
not ready"=20
repeated. So I looked</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in the -current for an update of the =
driver file.=20
The version of auich.c I have is 1.17. I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>found that version 1.18 in current =
(going back to=20
Aug 2002) had support for my </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>audio device and so included =
</FONT><FONT=20
face=3DArial size=3D2>it along with the corresponding auichreg.h and =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>recompiled my kernel. To get it to =
compile=20
</FONT><FONT face=3DArial size=3D2>I needed to remove on or two =
product</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> ID's which weren't in my version =
of=20
pcidevs.h.This worked </FONT><FONT face=3DArial size=3D2>fine and now I =
have=20
audio.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I have two questions: Firstly I am =
concerned as to=20
the impact of this ''hack". I think it should</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>not really affect much else but would =
like the=20
experts opinions.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Secondly I was wondering when the 1.6 =
branch of cvs=20
will be updated to include the fix</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>for this audio device?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Thank you in advance</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Ian</FONT></DIV></BODY></HTML>
------=_NextPart_000_06E4_01C3618E.7DF2A490--