public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
	openembedded-core@lists.openembedded.org
Subject: Re: Replacement for tslib?
Date: Thu, 1 Sep 2016 07:14:12 +0200	[thread overview]
Message-ID: <57C7B924.8050802@topic.nl> (raw)
In-Reply-To: <1472662673.29583.90.camel@linuxfoundation.org>

On 31-08-16 18:57, Richard Purdie wrote:
> On Wed, 2016-08-31 at 17:42 +0200, Enrico Scholz wrote:
>> Hello,
>>
>> tslib is more or less mandatory for resistive touchscreens but it was
>> removed some days ago.  This breaks e.g. meta-qt5 layer which depends
>> on it.
>>
>> Is this removal really final (which would be really bad, because
>> resistive
>> touchscreens are used e.g. in industrial environments)?
>
> The underlying pressure was from xcalibrate never having been merged
> into x11 and hence needing to replace xtscal by xinput-calibrate. With
> that change, the need for tslib wasn't clear.
>
> Its was also frustrating having two sets of pointercal files, one for
> xinput-calibrate and one for tslib.
>
> That said, I can see the need for tslib and if that is the only way to
> support these touchscreens in qt5/qt4 we might have to reconsider that.
>
> Are you sure the kernel interfaces that xinput is using don't work for
> qt4/qt5? If not, we may need to reconsider tslib...

Once reason to use Qt is the fact that you don't need X11 for it. And tslib is 
the only calibration tool that seems to work properly with resistive touchscreens.


      parent reply	other threads:[~2016-09-01  5:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 15:42 Replacement for tslib? Enrico Scholz
2016-08-31 16:57 ` Richard Purdie
2016-08-31 23:53   ` Enrico Scholz
2016-09-02 11:56     ` Burton, Ross
2016-09-02 12:34       ` Otavio Salvador
2016-09-02 12:43       ` Enrico Scholz
2016-09-02 12:54         ` Maxin B. John
2016-09-01  5:14   ` Mike Looijmans [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=57C7B924.8050802@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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