From: Jean Delvare <jdelvare@suse.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Oliver Neukum <oneukum@suse.de>,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Johan Hovold <johan@kernel.org>,
linux-input <linux-input@vger.kernel.org>
Subject: Re: quirk ALWAYS_POLL needed with an unexpectedly high number of mice
Date: Fri, 27 Mar 2015 16:59:29 +0100 [thread overview]
Message-ID: <1427471969.26270.7.camel@chaos.site> (raw)
In-Reply-To: <alpine.LNX.2.00.1503271609120.6781@pobox.suse.cz>
Le Friday 27 March 2015 à 16:10 +0100, Jiri Kosina a écrit :
> On Fri, 27 Mar 2015, Oliver Neukum wrote:
> > Keeping things as is is fine by me but then I will need to add a lot of
> > quirky devices.
>
> I am still surprised that all of a sudden there is such a large flow of
> new devices that need it, and we didn't have a single one a few months
> ago.
>
> Given the fact that this all is being reported by single entitty, is it a
> possibility that they have some other faulty HW instead? Such as the HUB
> suspending at random incorrect points in time?
I agree, I start wondering if maybe we've been barking up the wrong tree
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.
--
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
next prev parent reply other threads:[~2015-03-27 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 9:29 quirk ALWAYS_POLL needed with an unexpectedly high number of mice Oliver Neukum
2015-03-27 13:18 ` Benjamin Tissoires
2015-03-27 13:41 ` Oliver Neukum
2015-03-27 15:10 ` Jiri Kosina
2015-03-27 15:59 ` Jean Delvare [this message]
2015-03-27 16:09 ` Benjamin Tissoires
2015-03-27 16:11 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1427471969.26270.7.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=benjamin.tissoires@gmail.com \
--cc=jkosina@suse.cz \
--cc=johan@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=oneukum@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).