From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean Delvare Subject: Re: quirk ALWAYS_POLL needed with an unexpectedly high number of mice Date: Fri, 27 Mar 2015 16:59:29 +0100 Message-ID: <1427471969.26270.7.camel@chaos.site> References: <1427448571.5783.41.camel@suse.de> <1427463666.5783.55.camel@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from cantor2.suse.de ([195.135.220.15]:42017 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932154AbbC0P7d (ORCPT ); Fri, 27 Mar 2015 11:59:33 -0400 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Jiri Kosina Cc: Oliver Neukum , Benjamin Tissoires , Johan Hovold , linux-input Le Friday 27 March 2015 =C3=A0 16:10 +0100, Jiri Kosina a =C3=A9crit : > On Fri, 27 Mar 2015, Oliver Neukum wrote: > > Keeping things as is is fine by me but then I will need to add a lo= t of=20 > > quirky devices. >=20 > I am still surprised that all of a sudden there is such a large flow = of=20 > new devices that need it, and we didn't have a single one a few month= s=20 > ago. >=20 > Given the fact that this all is being reported by single entitty, is = it a=20 > possibility that they have some other faulty HW instead? Such as the = HUB=20 > suspending at random incorrect points in time? I agree, I start wondering if maybe we've been barking up the wrong tre= e since the beginning. I very much would like to know if all these "faulty" mouses would be so faulty when used on a different system. --=20 Jean Delvare SUSE L3 Support -- To unsubscribe from this list: send the line "unsubscribe linux-input" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html