All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6: Synaptics TouchPad and GPM (GPM patches)
Date: Fri, 22 Aug 2003 21:46:56 -0500	[thread overview]
Message-ID: <200308222146.56381.dtor_core@ameritech.net> (raw)

Hi,

Apologies for the semi-offtopic message but ever since support for 
Synaptics' absolute mode went in many people complained that it 
broke GPM. 

I did some work on extending evdev support in GPM, the new protocol
implementation supports following subtypes:

1. relative device - standard relative device like generic PS/2 mouse
   reporting via /dev/input/eventX
2. absolute device - touch screens and tablets.
3. touchpad - device reporting absolute coordinates and pressure via
   /dev/input/event, GPM recognizes normal and corner tapping.
4. synaptics - same as touchpad but also supports multi-finger taps
   (expects MSC_GESTURE messages from the kernel).

Kernel has to support EV_SYNC for touchpad and synaptics support, 
relative and absolute modes can be used with 2.4 kernels by specifying
nosync option.
 
You will find the patches at:
http://www.geocities.com/dt_or/gpm/patches/

RPMs (binary and source) built on RH8 are at:
http://www.geocities.com/dt_or/gpm/RPMS/

The README is at:
http://www.geocities.com/dt_or/gpm/gpm.html

The patches work pretty well for me and I hope they will work for others too.
Because of limited hardware I could not test evdev with touchscreen or a 
tablet.

Dmitry.

             reply	other threads:[~2003-08-23  2:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23  2:46 Dmitry Torokhov [this message]
2003-08-23  5:46 ` 2.6: Synaptics TouchPad and GPM (GPM patches) Joshua Kwan
2003-08-26  7:45 ` Vojtech Pavlik
2003-08-27  7:10   ` Dmitry Torokhov
2003-08-27 12:30     ` Vojtech Pavlik

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=200308222146.56381.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@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 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.