> The result is this:
> Before f13912d3f014a, if an RNDIS device has non-vendor-specific
> configurations after the first one, that one would be selected.
> After ff2a8c532c14, the first configuration would always be selected
> for RNDIS devices. Besides, there are several redundant checks in this
t; To: Greg Kroah-Hartman
> Cc: Nikolay Yakimov ; Gopal, Saranya
> ; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: [PATCH] USB: Fix configuration selection issues introduced in v4.20.0
>
> Commit f13912d3f014a introduced changes to the usb_choose_configura
; From: Con Kolivas [mailto:ker...@kolivas.org]
> Sent: Saturday, January 05, 2019 2:05 AM
> To: Gopal, Saranya
> Cc: Pierre-Louis Bossart ; Takashi Iwai
> ; alsa-de...@alsa-project.org; linux-...@vger.kernel.org;
> linux-kernel ; felipe.ba...@linux.intel.com
> Subject: Re: [al
> > [ Adding linux-usb ML to Cc, as it's a core USB issue ]
> >
> > So the device seems incorrectly advertising as if it were supporting
> > UAC3 -- assuming the device is still not UAC3-capable.
> >
> > IOW, it's a buggy firmware. We need some blacklisting, or revert the
> > commit for now, unles
4 matches
Mail list logo
