From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>, Peter Osterlund <petero2@telia.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: Broken synaptics mouse..
Date: Sun, 21 Sep 2003 18:16:36 -0500 [thread overview]
Message-ID: <200309211816.36783.dtor_core@ameritech.net> (raw)
In-Reply-To: <20030921172758.GA21014@ucw.cz>
On Sunday 21 September 2003 12:27 pm, Vojtech Pavlik wrote:
> On Sun, Sep 21, 2003 at 07:20:09PM +0200, Peter Osterlund wrote:
> > > I'd really prefer to contain the ugliness in mousedev.c, which then
> > > could be removed completely in 2.8 or so, when XFree and GPM is already
> > > well adapted to the event interface.
> >
> > That's certainly possible too. See patch below. Note though that this
> > patch has the disadvantage mentioned by Dmitry:
> >
> > We also can't just emulate relative events as everything is
> > multiplexed into /dev/input/mice and I can see many people
> > using Synaptics via /dev/input/eventX and everything else via
> > /dev/input/mice as it nicely handles hot plugging (at least I
> > use it this way).
>
> You can use EVIOCGRAB for the time being in the XFree86 synaptics
> driver, this way you'll prevent its events coming into mousedev the
> moment it's opened by XFree86, which is probably exactly what one wants.
>
Will that allow 2 processes to have access to the same event device
simultaneously? I am thinking about XFree and GPM. We just got away from
that mess caused by psaux providing only exclusive access to step into
the same problem again.
Dmitry
next prev parent reply other threads:[~2003-09-21 23:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0309110744030.28410-100000@home.osdl.org>
2003-09-18 23:43 ` Broken synaptics mouse Peter Osterlund
2003-09-19 5:05 ` Dmitry Torokhov
2003-09-19 11:48 ` Vojtech Pavlik
2003-09-21 17:20 ` Peter Osterlund
2003-09-21 17:27 ` Vojtech Pavlik
2003-09-21 19:29 ` Peter Osterlund
2003-09-21 19:34 ` Vojtech Pavlik
2003-09-21 20:26 ` Peter Osterlund
2003-09-21 20:42 ` Vojtech Pavlik
2003-09-21 23:16 ` Dmitry Torokhov [this message]
2003-09-22 5:31 ` Vojtech Pavlik
2003-09-22 5:58 ` Dmitry Torokhov
2003-09-22 6:09 ` Vojtech Pavlik
2003-10-01 10:03 ` Pavel Machek
2003-10-01 15:38 ` Peter Osterlund
[not found] <xgHm.3mL.27@gated-at.bofh.it>
[not found] ` <xlGW.2qw.15@gated-at.bofh.it>
2003-09-19 15:39 ` Ruben Puettmann
2003-09-21 21:17 Ricardo Galli
2003-09-21 21:41 ` Peter Osterlund
-- strict thread matches above, loose matches on Subject: below --
2003-09-21 22:15 Ricardo Galli
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=200309211816.36783.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--cc=torvalds@osdl.org \
--cc=vojtech@suse.cz \
/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