On Sun, 2 Dec 2007, Mark Lord wrote: > Reverting the drivers/hid directory does seem to improve behaviour. But > right now I have a "make -j4" happening in the background and the mouse > is ever so erratic again, despite the drivers/hid reversion. > So it's a timing thing, somewhere. Maybe a scheduling thing? Thanks a lot for your report Mark. Before we start digging deeply here -- Dmitry, do you think that this could be caused by your input-locking patches somehow? From Mark's report: - it didn't happen with 2.6.23 - when drivers/hid is put back into 2.6.23 state, the problem still persists in some sense So there must have been some change elsewhere (USB, Input, something completely different) that introduced this problem. > Jiri: I know nothing about how mouse clicks are interpreted, or even > *where* or *how* double-click detection happens. Until this started > happening, I didn't even know which module was the driver for my mouse > (it's usbhid). Can you give a short tutorial, to help us understand > possible causes ? First it would be really helpful to see if - the HID driver really obtains two click events from USB stack. This could be easily seen from HID debug output. I have written in previous mail how to obtain this - the output of evtest for the mouse device in /dev/input/event? (for determinign the correcnt event number corresponding to your mouse, see /proc/bus/input/devices) Thanks, -- Jiri Kosina SUSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
