Re: Logitech MX1000 Horizontal Scrolling

[Esben Stien <b0ef@esben-stien.name>]

Vojtech Pavlik <vojtech@suse.cz> writes:

> I don't think I have a patch for the MX1000 among them. I do have the
> MX1000, though, and I'm still thinking about what to do with it.

;)

> The problem is that the mouse really does reports all the double-button
> stuff and autorepeat, and horizontal wheel together with button press on
> wheel tilt.

This is a terrible hardware flaw if it can't be controlled.

Isnt't there a unique sequence we can determine when the horizontal
wheel is tilted?. When I turn off cruise control, all my buttons work
flawlessly, but not getting the autorepeat data. This autorepeat data
occurs between button press and button release and could be easily
forged.

> It has all that in the report descriptor, and the HID driver correctly
> interprets it and passes it on.

We should manipulate this data when it arrives in the kernel, in my
opinion. It's a faulty device and we should present it to userspace as
working.

> It's annoying, though.

Yeah, very, considering the capabilities of this device. 

> I could kill the extra buttons (via a HID quirk), which would leave us
> with autoscroll up/down/left/right, but the wheel wouldn't be
> distinguishable from the autoscroll anymore.

Not an option

> I can't kill the autoscroll alone and leave the buttons, because again
> the driver can't easily tell if it's the wheel or not.

I've killed the autoscroll by turning cruise control off; buttons work
then without auto repeat. I'm not sure what you mean here.

> In the end I think the best option is to leave the filtering to
> userspace, which will mean more configuration necessary in the X event
> mouse driver.

I hope this is not the final solution. I should be possible to disable
the data stream intervention if userspace wants to handle this, though.

-- 
Esben Stien is b0ef@esben-stien.name
http://www.esben-stien.name
irc://irc.esben-stien.name/%23contact
[sip|iax]:esben-stien.name