Daniel Mack wrote: > On Thu, Sep 02, 2010 at 01:13:48PM +0200, Clemens Ladisch wrote: > > I've got several reports that devices no longer work since UAC2 support got > > added. But I've just noticed this is not related to the interface class > > but to the interface protocol: the new code added checks for UAC_VERSION_1 > > or _2, but real devices apparently write just random junk into this field. > > (For vendor-specific interfaces, they are actually justified to do so.) > > Grr. So what about cases where this "random junk" is 0x20 by coincidence? Actually, it isn't too random: I've seen 0xff (obviously "vendor- specific") and 0x01/0x02 (interface subclass moved to protocol). Regards, Clemens _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
