On Fri, 27 Mar 2015, Benjamin Tissoires wrote: > Hmm... it looks like it's not host dependent unfortunately. We have a > (private) bug report for RHEL 6 where a customer wants to use the > following mouse: > http://www.compsource.com/pn/2MOUSEU1L/Keytronics-228/ > > I bought one and was able to reproduce the need for the quirk on > various systems. > > Plus I noticed that if the mouse is raised over the surface (so the > sensor does not report anything), the bug does not appear. > > So, to me, the USB output queue is full given that it is not polled by > the host and the chip within the USB mouse decides to > disconnect/reconnect to empty the queue. So nothing host specific. I am not questioning at all that it's needed for some devices. But I am surprised by all-of-a-sudden flow for quirk addition for many distinct devices, all coming from the same source. I am afraid this might be false positive, and root-cause being somewhere else, causing us adding a lot of potentially unnecessary quirk entries. -- Jiri Kosina SUSE Labs -- 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
