mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Daniel Ritz <daniel.ritz-ml@swissonline.ch>,
	daniel.ritz@gmx.ch, linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [PATCH] usb: generic calibration support
Date: Fri, 17 Nov 2006 15:22:06 +0000	[thread overview]
Message-ID: <1163776926.5551.28.camel@localhost.localdomain> (raw)
In-Reply-To: <200611171553.38164.hs4233@mail.mn-solutions.de>

On Fri, 2006-11-17 at 15:53 +0100, Holger Schurig wrote:
> > I believe tslib handles this.
> 
> The special X server "KDrive" supports tslib, this is used in 
> many embedded projects, e.g. by images created via 
> http://www.openembedded.org. But mainline X.org server, e.g. 
> what is in Debian unstable (7.1.0), doesn't support tslib.

Someone should add tslib support to the main xorg server then ;-). All
tslib supported devices will then just work...

> Also I don't know if X/tslib allows re-calibration on-the-fly, 
> but I guess it does. 

It does.

> However, tslib usually does not work via 
> the input subsystem (/dev/input/eventX is just one of them), 
> most devices use proprietary kernel interfaces.

tslib does work via the input subsystem for almost every 2.6 kernel
based device I can think of in OpenEmbedded and we made an active effort
to get into that position. The only proprietary interfaces are old 2.4
kernels.

> Qt/Embedded for Qt 2 and Qt 3 doesn't handle tslib 
> out-of-the-box, (heck, the don't even know 
> about /dev/input/eventX), but patches exist.

Qt/E 2/3 have a ton of other input issues beside this (e.e keymap
problems) so the lack of merged tslib support is only a minor one and as
you say, patches exist.

IMO, calibration in the kernel would be a backwards step (especially
when tslib can do more besides like filtering and hopefully in the
future rescaling).

Regards,

Richard


      reply	other threads:[~2006-11-17 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 10:25 Holger Schurig
2006-11-16 23:24 ` Daniel Ritz
2006-11-17  8:12   ` Holger Schurig
2006-11-17 14:16     ` Dmitry Torokhov
2006-11-17 14:53       ` Holger Schurig
2006-11-17 15:22         ` Richard Purdie [this message]

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=1163776926.5551.28.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=daniel.ritz-ml@swissonline.ch \
    --cc=daniel.ritz@gmx.ch \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®