From: "Thomas Munck Steenholdt" <tmus@get2net.dk>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Sv: i810 sound broken...
Date: Mon, 5 Aug 2002 13:45:27 +0200 [thread overview]
Message-ID: <200208051145.g75BjRN30389@eday-fe5.tele2.ee> (raw)
> 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)
That's strange - I get the same scratchy sounds on 2.4.19 as I did on 2.4.18 and a couple of the 2.4.19-pre's... Is there anything I should try, to make sure things are configged / built correctly..?
-- Send gratis SMS og brug gratis e-mail på Everyday.com --
next reply other threads:[~2002-08-05 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 11:45 Thomas Munck Steenholdt [this message]
2002-08-05 13:46 ` Alan Cox
2002-08-05 13:51 ` Jeff Chua
2002-08-05 13:07 Thomas Munck Steenholdt
2002-08-06 10:30 Thomas Munck Steenholdt
2002-08-06 14:29 ` Jeff Chua
2002-08-07 6:00 Thomas Munck Steenholdt
2002-08-07 7:51 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=200208051145.g75BjRN30389@eday-fe5.tele2.ee \
--to=tmus@get2net.dk \
--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®