From: Lauri Kasanen <cand@gmx.com>
To: linux-input@vger.kernel.org
Cc: thellstrom@vmware.com, dmitry.torokhov@gmail.com
Subject: MOUSE_PS2_VMMOUSE and input/mice
Date: Fri, 15 Jan 2016 12:39:28 +0200 [thread overview]
Message-ID: <20160115123928.d06e1fed.cand@gmx.com> (raw)
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
next reply other threads:[~2016-01-15 10:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 10:39 Lauri Kasanen [this message]
2016-01-15 11:08 ` MOUSE_PS2_VMMOUSE and input/mice Thomas Hellstrom
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=20160115123928.d06e1fed.cand@gmx.com \
--to=cand@gmx.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=thellstrom@vmware.com \
/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).