From: Vojtech Pavlik <vojtech@suse.cz>
To: Peter Osterlund <petero2@telia.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Vojtech Pavlik <vojtech@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: Broken synaptics mouse..
Date: Fri, 19 Sep 2003 13:48:06 +0200 [thread overview]
Message-ID: <20030919114806.GD784@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0309190129170.32637-100000@telia.com>
On Fri, Sep 19, 2003 at 01:43:11AM +0200, Peter Osterlund wrote:
> On Thu, 11 Sep 2003, Linus Torvalds wrote:
>
> > Actually, I think I've changed my mind.
> >
> > How hard would it be to have the "event" driver _notice_ when somebody is
> > trying to use it?
> >
> > In particular, what about something that
> > - just keeps the touchpad in "ps/2 compatibility mode" by default
> > - moves to absolute mode only if somebody actually uses the
> > /dev/input/event0 thing for it (and that would obviously disable the
> > ps/2 mode).
> >
> > That sounds like the simpler setup, especially since the touchpad does a
> > pretty good job of PS/2 emulation on its own..
>
> What do you think about the following patch? This patch makes the touchpad
> stay in compatibility mode until user space explicitly asks for absolute
> mode by sending a SYN_CONFIG event with value != 0 to the synaptics event
> device.
>
> I think this patch will apply on top of Vojtech's private tree, but I have
> lost track of what patches he said he has applied. Anyway, the whole patch
> series (14 patches) is available here:
>
> http://w1.894.telia.com/~u89404340/patches/touchpad/2.6.0-test5-bk5/v1/
>
> I dropped the "synaptics_optional" patch, because there should not be any
> need for the config option now that we have backwards compatibility by
> default.
The patch is nice and small, but I'm still not sure if we really want
input devices to have different modes, changing 'under hands' when one
process switches the mode while another is having the device open.
Things will then break.
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.
> linux-petero/drivers/input/mouse/psmouse-base.c | 2
> linux-petero/drivers/input/mouse/psmouse.h | 1
> linux-petero/drivers/input/mouse/synaptics.c | 62 ++++++++++++++++++++++--
> linux-petero/drivers/input/mouse/synaptics.h | 4 +
> 4 files changed, 63 insertions(+), 6 deletions(-)
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2003-09-19 11:53 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 [this message]
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
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=20030919114806.GD784@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--cc=torvalds@osdl.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