[alsa-devel] MUTE broken on hda nvhdmi
Hi. Mute seems to be broken since the nvhdmi rewrite. I'm currently using alsa-driver-1.0.23.0.g30ba4.0.g0c8e7.tar.bz2 -- anyone got plans to fix this on their TODO list or could please look into it?
Thanks.
At Mon, 10 May 2010 10:23:37 -0700, VDR User wrote:
Hi. Mute seems to be broken since the nvhdmi rewrite. I'm currently using alsa-driver-1.0.23.0.g30ba4.0.g0c8e7.tar.bz2 -- anyone got plans to fix this on their TODO list or could please look into it?
It's the first bug report I remember, so no one planned yet to fix :)
Please elaborate the problem first, and give alsa-info.sh (run with --no-upload option) at appropriate states for reference.
thanks,
Takashi
On Tue, May 11, 2010 at 2:07 AM, Takashi Iwai tiwai@suse.de wrote:
It's the first bug report I remember, so no one planned yet to fix :)
Strange, I saw another user mention he has the same problem. I swear it was on here but possibly the Nvidia support forums.
Please elaborate the problem first, and give alsa-info.sh (run with --no-upload option) at appropriate states for reference.
For example, if I press mute in VDR, nothing happens. However, mute worked fine using the alsa driver prior to the nvhdmi rewrite. I assume something was accidentally overlooked in the rewrite but you would know better than I.
Cheers
At Tue, 11 May 2010 08:28:39 -0700, VDR User wrote:
Please elaborate the problem first, and give alsa-info.sh (run with --no-upload option) at appropriate states for reference.
For example, if I press mute in VDR, nothing happens.
And what does this actually do from the driver perspective? Which control element is changed?
thanks,
Takashi
At Tue, 11 May 2010 17:36:36 +0200, I wrote:
At Tue, 11 May 2010 08:28:39 -0700, VDR User wrote:
Please elaborate the problem first, and give alsa-info.sh (run with --no-upload option) at appropriate states for reference.
For example, if I press mute in VDR, nothing happens.
And what does this actually do from the driver perspective? Which control element is changed?
Also, which change are you referring to as "nvhdmi rewrite"? Do you mean the commit "ALSA: hdmi - merge common code for intelhdmi and nvhdmi"?
Takashi
On Tue, May 11, 2010 at 8:47 AM, Takashi Iwai tiwai@suse.de wrote:
Also, which change are you referring to as "nvhdmi rewrite"? Do you mean the commit "ALSA: hdmi - merge common code for intelhdmi and nvhdmi"?
The rewritten code by Wei. What you quoted may be it as I don't think it was just nvhdmi that was rewritten, but other things as well.
At Tue, 11 May 2010 10:18:10 -0700, VDR User wrote:
On Tue, May 11, 2010 at 8:47 AM, Takashi Iwai tiwai@suse.de wrote:
Also, which change are you referring to as "nvhdmi rewrite"? Do you mean the commit "ALSA: hdmi - merge common code for intelhdmi and nvhdmi"?
The rewritten code by Wei. What you quoted may be it as I don't think it was just nvhdmi that was rewritten, but other things as well.
But I thought the driver didn't work before his patch to support MPC87 / GT221x? With which state are you comparing?
Takashi
On Tue, May 11, 2010 at 8:36 AM, Takashi Iwai tiwai@suse.de wrote:
For example, if I press mute in VDR, nothing happens.
And what does this actually do from the driver perspective? Which control element is changed?
I wouldn't have any clue, though I would assume mute means set the channel volume(s) to 0. That's a question for the guys actually writing the drivers I guess. All I know is mute works with pre-rewritten code, and not afterwards.
At Tue, 11 May 2010 10:17:13 -0700, VDR User wrote:
On Tue, May 11, 2010 at 8:36 AM, Takashi Iwai tiwai@suse.de wrote:
For example, if I press mute in VDR, nothing happens.
And what does this actually do from the driver perspective? Which control element is changed?
I wouldn't have any clue, though I would assume mute means set the channel volume(s) to 0. That's a question for the guys actually writing the drivers I guess. All I know is mute works with pre-rewritten code, and not afterwards.
Then revert to the previous version, and check alsa-info.sh before and after toggling the mute control to identify what it actually does.
Right now, it's like shooting in a dark to the direction you say "hey it's there" :)
Takashi
participants (2)
-
Takashi Iwai -
VDR User