From: Takashi Iwai <tiwai@suse.de>
To: "David Gómez" <dabisu@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Intel8x0 still broken in 2.6.9-ac16
Date: Fri, 17 Dec 2004 16:39:28 +0100 [thread overview]
Message-ID: <s5hsm65vsr3.wl@alsa2.suse.de> (raw)
In-Reply-To: <ae4c715704121614542739c909@mail.gmail.com>
At Thu, 16 Dec 2004 23:54:07 +0100,
David Gómez wrote:
>
> Hi,
>
> I downloaded ac16 because i saw that a fix from Takashi was included
> in previous ac12 patch. In summary: sound is still broken in
> 2.6.9-ac16 for the snd_intel8x0 alsa driver, but it's working in
> 2.6.8.
>
> Errors it get,
>
> When playing mp3 file:
>
> codec_read 0: semaphore is not ready for register 0x2c
> codec_read 0: semaphore is not ready for register 0x2c
> codec_read 0: semaphore is not ready for register 0x2c
> ...
>
> When changing mixer settings with alsamixer:
>
> codec_write 0: semaphore is not ready for register 0x2
> codec_write 0: semaphore is not ready for register 0x2
> codec_write 0: semaphore is not ready for register 0x2
This implies that wrong SDI's are assigned to the codec or GLOB_STA
register shows something different.
Please attach /proc/asound/card0/intel8x0 and
/proc/asound/card0/codec97#0/* files for debugging.
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-17 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 22:54 Intel8x0 still broken in 2.6.9-ac16 David Gómez
2004-12-17 15:39 ` Takashi Iwai [this message]
2004-12-17 17:38 ` David Gómez
2004-12-20 18:14 ` Takashi Iwai
[not found] ` <ae4c71570412201519597d596a@mail.gmail.com>
2004-12-21 10:20 ` Takashi Iwai
[not found] ` <ae4c715704122111563be9a075@mail.gmail.com>
2004-12-22 14:53 ` Takashi Iwai
2004-12-22 19:22 ` David Gómez
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=s5hsm65vsr3.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dabisu@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).