From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Chuck Ebbert" <cebbert@redhat.com>
Cc: "Pete Zaitcev" <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org,
linux-input@atrey.karlin.mff.cuni.cz,
"Peter Osterlund" <petero2@telia.com>
Subject: Re: Fix sudden warps in mousedev
Date: Tue, 27 Mar 2007 11:46:04 -0400 [thread overview]
Message-ID: <d120d5000703270846y87e4283m4009ff0a9f65dac4@mail.gmail.com> (raw)
In-Reply-To: <460934D7.9030700@redhat.com>
On 3/27/07, Chuck Ebbert <cebbert@redhat.com> wrote:
> Dmitry Torokhov wrote:
> >
> > The driver grabs tochpad with EVIOCGRAB ioctl to prevent input events
> > from bveing delivered to X through /dev/input/mice which is still in
> > whidespread use. That's why evtest does not work. We could as Peter
> > (CCed) to implement an option to turn off grabbing so users who don't
> > use mousedev multiplexor can use evtest and other commands.
> >
>
> What should people be using instead of /dev/input/mice ?
/dev/input/mice is most convenient source untill X gets hotplug ability.
>
> And why did the mouse numbers all get rearranged in 2.6.20, e.g.
> mouse1 became mouse2 for many people?
Input devices are not guaranteed to be stable.
--
Dmitry
next prev parent reply other threads:[~2007-03-27 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 7:16 Fix sudden warps in mousedev Pete Zaitcev
2007-03-24 7:16 ` Pete Zaitcev
2007-03-25 5:34 ` Dmitry Torokhov
2007-03-25 18:19 ` Pete Zaitcev
2007-03-26 3:19 ` Dmitry Torokhov
2007-03-26 19:17 ` Pete Zaitcev
2007-03-26 19:30 ` Dmitry Torokhov
2007-03-26 21:42 ` Pete Zaitcev
2007-03-27 1:14 ` Dmitry Torokhov
2007-03-27 15:14 ` Chuck Ebbert
2007-03-27 15:46 ` Dmitry Torokhov [this message]
2007-03-27 16:04 ` Chuck Ebbert
2007-03-27 16:19 ` Dmitry Torokhov
2007-03-28 20:51 ` Matt Keenan
2007-04-11 21:51 ` Peter Osterlund
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=d120d5000703270846y87e4283m4009ff0a9f65dac4@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=cebbert@redhat.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--cc=zaitcev@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.