public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-Input <linux-input@atrey.karlin.mff.cuni.cz>
Subject: Re: [RFC/RFT] [patch] Elo serial touchscreen driver
Date: Wed, 9 Feb 2005 21:06:46 +0100	[thread overview]
Message-ID: <20050209200646.GL10594@lug-owl.de> (raw)
In-Reply-To: <420A6A5C.8030106@grupopie.com>

[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]

On Wed, 2005-02-09 19:54:04 +0000, Paulo Marques <pmarques@grupopie.com>
wrote in message <420A6A5C.8030106@grupopie.com>:
> >We could have a library that would do that and link applications against
> >it. It could also handle things like tap-n-drag, etc, something we
> >certainly don't want in the kernel.
> 
> I really like this idea :)
> 
> A libtouch library that handled calibration (this includes mirroring and 
> swapping the coordinates) and other goodies (like filtering out short 
> "touch release" events while dragging, etc.) would be a good standard 
> interface for all applications.
>
> Being in user space would also mean that the library could do things 
> like keeping a /etc/touch.conf file where it would read default 
> calibration data, etc.

...and for X11. Maybe we'd start talking about an API for this lib? At
least, my employer is interested I guess. (But this is OT wrt. the Linux
kernel, could you contact me at jbglaw@microdata-pos.de?)

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-02-09 20:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 16:42 [RFC/RFT] [patch] Elo serial touchscreen driver Vojtech Pavlik
2005-02-08 16:54 ` Dmitry Torokhov
2005-02-09 13:23 ` Paulo Marques
2005-02-09 17:00   ` Vojtech Pavlik
2005-02-09 17:14     ` Jan-Benedict Glaw
2005-02-09 17:30       ` Vojtech Pavlik
2005-02-09 18:08         ` Paulo Marques
2005-02-09 19:18           ` Vojtech Pavlik
2005-02-09 19:54             ` Paulo Marques
2005-02-09 20:06               ` Jan-Benedict Glaw [this message]
2005-02-09 20:03             ` Jan-Benedict Glaw
2005-02-09 20:10               ` Vojtech Pavlik
2005-02-09 21:53                 ` Jan-Benedict Glaw
2005-02-09 19:58           ` Jan-Benedict Glaw
2005-02-09 20:51             ` Paulo Marques
2005-02-09 21:39               ` Jan-Benedict Glaw
2005-02-09 21:53                 ` Vojtech Pavlik
2005-02-10 10:46                   ` Jan-Benedict Glaw
2005-02-10 13:06                     ` Paulo Marques
2005-02-10 13:43                       ` Jan-Benedict Glaw
2005-02-10 15:35                         ` Paulo Marques
2005-02-10 15:55                           ` Jan-Benedict Glaw
2005-02-10 16:16                           ` 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=20050209200646.GL10594@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    --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