public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: dtor_core@ameritech.net
Cc: Hans-Christian Egtvedt <hc@mivu.no>,
	linux-kernel@vger.kernel.org,
	linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] new driver for ITM Touch touchscreen
Date: Tue, 8 Mar 2005 18:49:46 +0100	[thread overview]
Message-ID: <20050308174946.GA2202@ucw.cz> (raw)
In-Reply-To: <d120d500050308092554b49728@mail.gmail.com>

On Tue, Mar 08, 2005 at 12:25:09PM -0500, Dmitry Torokhov wrote:

> I am not sure... that BTN_TOUCH - look slike it works off a single
> flag reported by hardware. You porobably do not need to change it.

Indeed, if the hardware reports a touch flag it's best to use that.

> Try loading mousedev module (after adding input_sync back to your
> driver) - it provides cooked PS/2 protocol to userspace - it should
> bind to your driver. Then you can use GPM or X (read from
> /dev/input/mice) to test the touchscreen and see if you have issue
> with double clicks.
 
And for even better behavior, use 'evtouch' from Kenan Esau as an X
driver.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2005-03-08 17:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 10:30 [PATCH] new driver for ITM Touch touchscreen Hans-Christian Egtvedt
2005-03-04 12:03 ` Alexey Dobriyan
2005-03-04 14:52   ` Dmitry Torokhov
2005-03-04 16:20     ` Hans-Christian Egtvedt
2005-03-04 16:54       ` Dmitry Torokhov
2005-03-04 18:51         ` Hans-Christian Egtvedt
2005-03-04 20:38           ` Vojtech Pavlik
2005-03-04 20:35         ` Vojtech Pavlik
2005-03-08 16:01         ` Hans-Christian Egtvedt
2005-03-08 17:25           ` Dmitry Torokhov
2005-03-08 17:49             ` Vojtech Pavlik [this message]
2005-03-08 18:23           ` Paulo Marques
2005-03-10 16:18           ` Vojtech Pavlik
2005-03-10 16:41             ` Hans-Christian Egtvedt
2005-03-10 16:46               ` 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=20050308174946.GA2202@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dtor_core@ameritech.net \
    --cc=hc@mivu.no \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox