From: Juergen Sawinski <juergen.sawinski@mpimf-heidelberg.mpg.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "linux-kernel@vger" <linux-kernel@vger.kernel.org>
Subject: Re: i810 sound broken...
Date: 05 Aug 2002 22:21:00 +0200 [thread overview]
Message-ID: <1028578861.1894.15.camel@voyager> (raw)
In-Reply-To: <1028552057.18130.6.camel@irongate.swansea.linux.org.uk>
On my Intel D845GBV board (obviously ICH4) none of 2.4 nor alsa works.
It's a production box, so I hestitate to try 2.5.
George
P.S.: Alan, any hints how I can examine/fix this?
On Mon, 2002-08-05 at 14:54, Alan Cox wrote:
> On Mon, 2002-08-05 at 12:27, Thomas Munck Steenholdt wrote:
> > I've noticed some writing on lkml on how i810(AC97) sound was broken.
> > Aparantly a couple of fixes have been posted, but I couldn't see
> > where(if at all) those patches have gone... 2.4.19 still does not work
> > and 2.4.19-ac3 won't even load the i810 module.
> >
> > Does anybody know if the known i810 sound issue has, in fact, been fixed, and if so - in what kernel/patch?
>
> Its working nicely for me in 2.4.19 and 2.4.19-ac1. The 2.4.19-ac3 tree
> has a bug in pci_enable_device which will stop it working if built with
> some compilers (by chance it works ok the way I tested it). Thats fixed
> in ac4.
>
> The changes in the recent i810 audio are
> - Being more pessimistic in our interpretation of codec power up
> - Turning on EAPD in case the BIOS didn't do so at boot up
>
> Longer term full EAPD control as we do with the cs46xx is on my list,
> paticularly as i8xx laptops are becoming common . (EAPD is the amplifier
> power controller)
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Juergen Sawinski
Max-Planck-Institute for Medical Research
Dept. of Biomedical Optics
Jahnstr. 29
D-69120 Heidelberg
Germany
Phone: +49-6221-486-309
Fax: +49-6221-486-325
priv.
Phone: +49-6221-418 848
Mobile: +49-171-532 5302
next prev parent reply other threads:[~2002-08-05 20:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 11:27 Thomas Munck Steenholdt
2002-08-05 12:54 ` Alan Cox
2002-08-05 13:47 ` venom
2002-08-05 15:28 ` Alan Cox
2002-08-05 18:38 ` Thomas Munck Steenholdt
2002-08-06 0:26 ` Jeff Chua
2002-08-07 15:05 ` Doug Ledford
2002-08-07 18:49 ` Juergen Sawinski
2002-08-08 20:47 ` Doug Ledford
2002-08-05 21:38 ` Alexander Hoogerhuis
2002-08-06 14:47 ` Alan Cox
2002-08-06 13:31 ` Alexander Hoogerhuis
2002-08-05 20:21 ` Juergen Sawinski [this message]
2002-08-05 21:44 ` Alan Cox
2002-08-06 7:24 Andris Pavenis
2002-08-08 8:37 Thomas Munck Steenholdt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1028578861.1894.15.camel@voyager \
--to=juergen.sawinski@mpimf-heidelberg.mpg.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®