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] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c7b2c6b-5dcc-7170-f6e1-bf6021bbb72a@linux.intel.com>
Date:   Fri, 4 Jan 2019 09:23:38 -0600
From:   Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To:     Takashi Iwai <tiwai@...e.de>, Con Kolivas <kernel@...ivas.org>
Cc:     saranya.gopal@...el.com, alsa-devel@...a-project.org,
        linux-usb@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>,
        felipe.balbi@...ux.intel.com
Subject: Re: [alsa-devel] ALSA:usb audio Higher sample rates on usb audio no
 longer working.


> [ 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, unless any real UAC3 device comes up to the market.

IIRC an UAC3-capable device is required to expose a backwards-compatible 
configuration (either UAC1 or UAC2). Maybe an additional test can be 
done to harden the detection so that UAC3 is only chosen if indeed a 
second audio configuration is present as well.

I also vaguely recall there was talk about adding information in the BOS 
descriptor, but I don't know if this was ever published.

-Pierre

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ