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
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
