linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: Lauri Kasanen <cand@gmx.com>, linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com
Subject: Re: MOUSE_PS2_VMMOUSE and input/mice
Date: Fri, 15 Jan 2016 12:08:51 +0100	[thread overview]
Message-ID: <5698D343.3000606@vmware.com> (raw)
In-Reply-To: <20160115123928.d06e1fed.cand@gmx.com>

On 01/15/2016 11:39 AM, Lauri Kasanen wrote:
> Hi,
>
> 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?
>
> - Lauri

Hi, Lauri.
What particular use-case is broken?

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.

/Thomas




  reply	other threads:[~2016-01-15 11:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 10:39 MOUSE_PS2_VMMOUSE and input/mice Lauri Kasanen
2016-01-15 11:08 ` Thomas Hellstrom [this message]
2016-01-15 11:23   ` Lauri Kasanen
2016-01-15 15:45     ` Thomas Hellstrom
2016-01-15 17:50       ` Dmitry Torokhov
2016-01-15 18:22         ` Thomas Hellstrom
2016-01-16 15:39           ` Lauri Kasanen
2016-01-16 18:16             ` Dmitry Torokhov
2016-01-18  8:30               ` Lauri Kasanen
2016-01-16  8:57         ` Lauri Kasanen
2016-01-16 18:30           ` Dmitry Torokhov
2016-01-16 19:10             ` Lauri Kasanen
2016-01-16 19:38               ` Dmitry Torokhov
2016-01-17  9:32                 ` Lauri Kasanen

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=5698D343.3000606@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=cand@gmx.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).