From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Lauri Kasanen <cand@gmx.com>
Cc: Thomas Hellstrom <thellstrom@vmware.com>, linux-input@vger.kernel.org
Subject: Re: MOUSE_PS2_VMMOUSE and input/mice
Date: Sat, 16 Jan 2016 11:38:08 -0800 [thread overview]
Message-ID: <20160116193808.GG9203@dtor-ws> (raw)
In-Reply-To: <20160116211011.6aeff246.cand@gmx.com>
On Sat, Jan 16, 2016 at 09:10:11PM +0200, Lauri Kasanen wrote:
> On Sat, 16 Jan 2016 10:30:08 -0800
> Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
>
> > > > 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.
> > >
> > > TinyCore sends their regards, and tells they will consider evdev when
> > > Xorg + evdev + paraphelia can total less than 650kb.
> >
> > I do not think you are doing your users any favors by limiting them to
> > PS/2 emulation. For desktops, unless they only use basic mice mousedev
> > emulation does not work well for neither touchpads, nor tablets, nor
> > touchscreens. And for appliances you do not need mouse at all. Maybe if
> > you targeting kiosks with limited UI it will work for a bit. I wonder
> > how long Xorg will be keeping lights on for mouse_drv.
> >
> > I am tempted to deprecate mousedev and maybe joydev as well. They were
> > supposed to fill the gap between then current applications and kernel,
> > but that was 10+ years ago.
>
> Hi,
>
> It's a choice we leave up to the users. The majority uses normal
> desktops with normal mice, touch screens and tablets tend to be a
> rarity in our userbase. So we can serve the majority without the bloat
> of Xorg, but those who need it can install it.
So people who do not need Xorg do not need the mouse either, right? I am
still confused who your target user base is.
>
> That's why I was asking for a runtime way - the default should work,
> but so should VMWare's nicer mouse integration when Xorg is installed.
> That concern was resolved with the statement the older support is not
> being considered for removal. The original issue will be solved by
> disabling VMMOUSE in our kernel.
I guess you can disable this (bit then you need to carry Xorg vmmouse
driver), but then you'll still have to pay the piper once Xorg drops
root support and X vmmouse driver will not be able to access the
hypervisor port.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2016-01-16 19:38 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
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 [this message]
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=20160116193808.GG9203@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=cand@gmx.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).