On Sat, 28 Nov 2009, Guido Dorssers wrote: > > The problem apparently [1] is, that the vendor has been super-creative and > > assigned the same combination of idVendor/idProduct to completely > > different devices. Oh well. > > > > Remi, could you please check your device against the lsusb data provided > > in bugzilla to check whether there is any possibility to distinguish these > > devices, so that we could put some ugly check in place probably? > > > > Thanks. > > > > [1] http://lkml.org/lkml/2009/2/10/434 > > > > Hi all, > > A belated thanks for having pointed me into the right direction to get my > barcodescanner operational. However, as a thought since the bug is still > present, why not solve it with something as simple as making the blacklisting > user-configurable instead of blacklisting valid HID devices on purpose? Hi, actually, my current plan is to remove the blacklist entry for this combination of VID/PID completely, and let the user decide and unbind the driver via sysfs eventually, if needed (maybe together with warning in dmesg). As the vendor apparently messed up horribly, as far as I understand, I don't really see another option. -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
