From: Thomas Hellstrom <thellstrom@vmware.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Lauri Kasanen <cand@gmx.com>, linux-input@vger.kernel.org
Subject: Re: MOUSE_PS2_VMMOUSE and input/mice
Date: Fri, 15 Jan 2016 19:22:31 +0100 [thread overview]
Message-ID: <569938E7.3090509@vmware.com> (raw)
In-Reply-To: <20160115175040.GA5664@dtor-ws>
On 01/15/2016 06:50 PM, Dmitry Torokhov wrote:
> On Fri, Jan 15, 2016 at 04:45:28PM +0100, Thomas Hellstrom wrote:
>> On 01/15/2016 12:23 PM, Lauri Kasanen wrote:
>>> On Fri, 15 Jan 2016 12:08:51 +0100
>>> Thomas Hellstrom <thellstrom@vmware.com> 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.
> Although we will make vmmouse work with /dev/input/mice, could you
> please tell TinyCore that 90s are calling and they want their mouse
> technology back? And tell them to switch to switch to evdev X driver.
>
>>>> 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.
> No, this is not correct, mousedev (the one that provides
> /dev/input/mouseX and /dev/input/mice) should bind to absolute device
> exported by vmmouse on this rule:
>
> {
> .flags = INPUT_DEVICE_ID_MATCH_EVBIT |
> INPUT_DEVICE_ID_MATCH_KEYBIT |
> INPUT_DEVICE_ID_MATCH_ABSBIT,
> .evbit = { BIT_MASK(EV_KEY) | BIT_MASK(EV_ABS) },
> .keybit = { [BIT_WORD(BTN_LEFT)] = BIT_MASK(BTN_LEFT) },
> .absbit = { BIT_MASK(ABS_X) | BIT_MASK(ABS_Y) },
> }, /* Mouse-like device with absolute X and Y but ordinary
> clicks, like hp ILO2 High Performance mouse */
>
> and it should convert absolute events to relative motion.
>
Ah. Thanks for clarifying!
/Thomas
next prev parent reply other threads:[~2016-01-15 18:22 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
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 [this message]
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=569938E7.3090509@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).