From: Alexey Fisher <bug-track@fisher-privat.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [regression] probably in mixer.c code
Date: Tue, 08 Nov 2011 13:39:38 +0100 [thread overview]
Message-ID: <4EB9230A.1040607@fisher-privat.net> (raw)
In-Reply-To: <s5hwrbag6fh.wl%tiwai@suse.de>
Am 08.11.2011 13:11, schrieb Takashi Iwai:
> At Tue, 08 Nov 2011 12:25:06 +0100,
> Alexey Fisher wrote:
>>
>> Am 08.11.2011 10:59, schrieb Takashi Iwai:
>>> At Tue, 08 Nov 2011 09:49:13 +0100,
>>> Alexey Fisher wrote:
>>>>
>>>> Hallo all, Takashi,
>>>>
>>>> there is one regression in current linux main tree:
>>>>
>>>> cval->res quirks do not work any more. See usb/mixer.c:1150
>>>> Are there was some work in this area or may be some one bisected this
>>>> bug down?
>>>
>>> Are you referring to the device 046d:09a4, which sets the mixer range
>>> manually? If yes, does the patch below work?
>>>
>>
>>
>> No, i referring to devices 046d:0991, 046d:081d, i don't have access to
>> 046d:09a4.
>>
>> This part is broken for me:
>> case USB_ID(0x046d, 0x0991):
>> /* Most audio usb devices lie about volume resolution.
>> * Most Logitech webcams have res = 384.
>> * Proboly there is some logitech magic behind this number --fishor
>> */
>> if (!strcmp(kctl->id.name, "Mic Capture Volume")) {
>> snd_printk(KERN_INFO
>> "set resolution quirk: cval->res = 384\n");
>> cval->res = 384;
>> }
>> break;
>
> OK, so _what_ is actually broken? Do you see the message but
> cval->res is overridden later?
yes.
next prev parent reply other threads:[~2011-11-08 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 8:49 [regression] probably in mixer.c code Alexey Fisher
2011-11-08 9:59 ` Takashi Iwai
2011-11-08 11:25 ` Alexey Fisher
2011-11-08 12:11 ` Takashi Iwai
2011-11-08 12:39 ` Alexey Fisher [this message]
2011-11-08 13:05 ` Takashi Iwai
2011-11-08 13:09 ` Takashi Iwai
2011-11-08 14:32 ` Alexey Fisher
2011-11-08 14:54 ` Takashi Iwai
2011-11-08 16:46 ` Alexey Fisher
2011-11-08 16:55 ` Takashi Iwai
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=4EB9230A.1040607@fisher-privat.net \
--to=bug-track@fisher-privat.net \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.