From: Oliver Neukum <oneukum@suse.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-usb@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 1/2] usbhid: more mice with ALWAYS_POLL
Date: Wed, 08 Apr 2015 09:33:11 +0200 [thread overview]
Message-ID: <1428478391.6579.3.camel@suse.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1504021425550.843@pobox.suse.cz>
On Thu, 2015-04-02 at 14:26 +0200, Jiri Kosina wrote:
> On Wed, 1 Apr 2015, Oliver Neukum wrote:
>
> > > I am postponing all these before it is clarified that this is indeed a
> > > case reporter is able to reproduce on different system as well to rule out
> > > the possibility of hub being the actual root cause.
> >
> > The test has been redone on a different system with a mouse reported to
> > be affected and the problem does show up. I have to conclude that the we
> > are really a victim of bias here. We thought the issue was rare because
> > we never looked for it.
>
> Ok, this is sad.
>
> I am now applying these two on the previous ones, and we'll see. If this
> becomes a frequently re-appearing topic, we'll have to come up with more
> generic aproach.
I think it is unacceptable to punish owners of good mice for quirky
stuff, yet the current approach of manually setting quirks from a module
option or adding them to the blacklist has drawbacks.
1. It is slow and cumbersome (especially the blacklist)
2. adding the quirk requires root rights, foreknowledge and is limited
to 4 devices
So at this point. I'd say the best option would be to have a module
parameter to tell HID that it should assume all devices to be quirky.
Regards
Oliver
parent reply other threads:[~2015-04-08 7:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.LNX.2.00.1504021425550.843@pobox.suse.cz>]
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=1428478391.6579.3.camel@suse.de \
--to=oneukum@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.