On Fri, 15 Jan 2016 12:08:51 +0100 Thomas Hellstrom <thellstrom@xxxxxxxxxx> wrote: > > Seems the new and shiny VMWare mouse driver does not pass events > > to /dev/input/mice, rudely breaking userspace that doesn't > > support absolute input devices. > > > > Can this be changed? Would there be any downside to passing those > > events? > > Hi, Lauri. > What particular use-case is broken? VMWare + 4.2 kernel + Xvesa. This was reported for the current TinyCore beta, which has that kernel. > I'm assuming what's happening is that only the relative device gets > recognized as a mouse, and by default we don't send events through that > device. > > In the vmware gui there is a workaround, one can select > edit->preferences->input->"Optimize mouse for games"->Always > > This will send events through the relative USB mouse, and if there is no > USB controller in the VM, through the relative MOUSE_PS2_VMMOUSE > > The other option is to limit the number of protocols the PS2 driver > checks for and avoid enabling the vmmmouse functionality. There is a > kernel module option for that, although I can't remember it offhand. > > We can't send both relative and absolute events simultaneously since > that would confuse the X server severely. Yeah, I know of the psmouse.proto=imps workaround. But requiring either bootcodes or VM setting tweaks is not nice, as what the users see will be "distro version X worked in my VMWare, in version Y the mouse does not work". If we instead disable MOUSE_PS2_VMMOUSE, I assume a future xf86-input-vmmouse version will drop support for the userspace-side mouse synchronization, and then VMWare+Xorg users will suffer. Can you think of any solution that would detect things at runtime? - Lauri -- 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
