On Wed, 13 Sep 2017, jikos@xxxxxxxxxx wrote: > On Wed, 13 Sep 2017, benjamin.tissoires@xxxxxxxxxx wrote: > > > I do not see a reason not to. Maybe Jiri will, but the fact that one > > version works and one doesn't seem enough to allow such specific > > blacklisting. > > The blacklist matching currently doesn't support that, but it'd be trivial to match, and I > actually think it generally makes sense to me. So feel free (once you guys settle on > solution that both Chromium and Jabr folk find acceptable) to send this together with > a hid-core patch that'd add a possibility to perform per-fw-version matching. Great! Shall I give it a shot? Or is there someone with more intimate knowledge about hid-core that wants to do it? How should it work? A simple setup would be to attach an optional list of blacklisted firmware versions to each entry in hid_ignore_list[]? If this list is empty, all firmware versions are blacklisted. The attached list could just be a static array. Would this be acceptable? Thanks, Niels **** GN GROUP NOTICE - AUTOMATICALLY INSERTED**** The information in this e-mail (including attachments, if any) is considered confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this e-mail is prohibited except by or on behalf of the intended recipient. If you have received this email in error, please notify me immediately by reply e-mail, delete this e-mail, and do not disclose its contents to anyone. Any opinions expressed in this e-mail are those of the individual and not necessarily the GN group. Thank you. ******************** DISCLAIMER END ************************ -- 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
