From: Takashi Iwai <tiwai@suse.de>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [RFE] Power down AC'97 when muted
Date: Mon, 27 Dec 2004 15:05:46 +0100 [thread overview]
Message-ID: <s5hr7lbdef9.wl@alsa2.suse.de> (raw)
In-Reply-To: <41CB14F9.6060306@drzeus.cx>
At Thu, 23 Dec 2004 19:56:57 +0100,
Pierre Ossman wrote:
>
> Takashi Iwai wrote:
>
> >
> >It's BUG #667, right?
> > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=667
> >
> >I uploaded a test patch there. Please give it a try.
> >
> >
> >
> Yup, seems to be the same thing. I tried the patch and got it working
> after a few tweaks:
>
> * None of the parts applied cleanly. You had a strange path to
> ac97_codec.h and you also seemed to have a newer version of the driver
> than I had (2.6.9 here).
It's to alsa-kernel tree. It's not to the linux kernel tree.
> * My card had a different subsystem vendor that in the patch:
> {
> .vendor = 0x0e11,
> .device = 0x0860,
> .name = "HP/Compaq nx7010",
> .type = AC97_TUNE_MUTE_LED
> },
Added.
> * The new function called set_single not set_double which caused all
> kinds of strange effects.
>
> I also noted another "feature". The quirk seems to take some time to go
> into effect since the LED doesn't light up if the mute is enabled
> directly after the module is loaded (done by scripts in FC3 during
> module load).
Fixed on CVS version.
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/
prev parent reply other threads:[~2004-12-27 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 19:41 [RFE] Power down AC'97 when muted Pierre Ossman
2004-12-23 15:10 ` Takashi Iwai
2004-12-23 18:56 ` Pierre Ossman
2004-12-27 14:05 ` Takashi Iwai [this message]
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=s5hr7lbdef9.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=drzeus-list@drzeus.cx \
/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