linux-kernel - Re: [PATCH SND/USB]: Add QuickCam Communicate Deluxe/S7500 to volume_control

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 09 Dec 2016 21:53:39 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     Con Kolivas <kernel@...ivas.org>
Cc:     linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH SND/USB]: Add QuickCam Communicate Deluxe/S7500 to  volume_control_quirks.

On Fri, 09 Dec 2016 21:35:17 +0100,
Con Kolivas wrote:
> 
> On Friday, 9 December 2016 11:22:15 AM AEDT Takashi Iwai wrote:
> > On Fri, 09 Dec 2016 05:15:57 +0100,
> > 
> > Con Kolivas wrote:
> > > The Logitech QuickCam Communicate Deluxe/S7500 microphone fails with the
> > > following warning.
> > > 
> > > [    6.778995] usb 2-1.2.2.2: Warning! Unlikely big volume range (=3072),
> > > cval->res is probably wrong.
> > > [    6.778996] usb 2-1.2.2.2: [5] FU [Mic Capture Volume] ch = 1, val =
> > > 4608/7680/1
> > > 
> > > Adding it to the list of devices in volume_control_quirks makes it work
> > > properly, fixing related typo.
> > > 
> > > Signed-off-by: Con Kolivas <kernel@...ivas.org>
> > 
> > Applied (with Cc to stable), thanks.
> 
> (Apologies for google mail defaulting to html, resending with a proper mail 
> client)
> 
> You're welcome. As there appear to be a lot of these devices from the same 
> manufacturer with the same error, and there are likely a lot of devices out 
> there that are missed from this whitelist, do you think it would be worthwhile 
> changing the code to detect the combination of unlikely big volume range and 
> usb vendor of 0x046d and automatically try using the volume_control_quirk on 
> them instead of a discrete whitelist?

Yeah, it sounds like a good idea!


thanks,

Takashi