Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Simon Busch <morphis@gravedo.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core 1/4] qt4-embedded: remove dependency on tslib and use std. linux input
Date: Wed, 12 Oct 2011 21:52:11 +0200	[thread overview]
Message-ID: <4E95EFEB.6040204@gravedo.de> (raw)
In-Reply-To: <4E95EA85.5040301@gravedo.de>

On 12.10.2011 21:29, Simon Busch wrote:
> On 12.10.2011 21:24, Simon Busch wrote:
>> On 12.10.2011 21:09, Koen Kooi wrote:
>>>> What is breaking qt:e in this case? For me it's just a feature reduction
>>>> and not a break (as qt:e still works fine with the linux input interface).
>>>
>>> When your TS is suddenly uncalibrated and jittery, it's a breakage, not a feature reduction.
>>
>> You're talking here about one case where tslib is needed to get a
>> working touchscreen. But there are even cases where tslib is not needed
>> to get a working touchscreen.
>>
>> qt:e does not strongly depends on tslib, it can work without. So if you
>> need it you should add it to your machine layer as it is really machine
>> specific if you need tslib or not.
> 
> Eric brings it to the point, only resetting the qte.sh script to a
> default one which uses a linux input even node should be enough.

Sorry for my little generic trip ... :)

I will provide another patch in the following days which just makes
qte.sh use of a std. linux input dev node instead of a tslib one if
nobody has any objections against this.

regards,
Simon

-- 
Simon Busch - http://mm.gravedo.de/blog/



  reply	other threads:[~2011-10-12 19:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12  7:44 [oe-core 0/4] Qt4, armv6, xserver-xorg changes Martin Jansa
2011-10-12  7:45 ` [oe-core 1/4] qt4-embedded: remove dependency on tslib and use std. linux input Martin Jansa
2011-10-12  8:02   ` Eric Bénard
2011-10-12  9:20     ` Koen Kooi
2011-10-12 19:04       ` Chris Larson
2011-10-12 18:10     ` Simon Busch
2011-10-12 18:14       ` Koen Kooi
2011-10-12 18:34         ` Simon Busch
2011-10-12 19:09           ` Koen Kooi
2011-10-12 19:24             ` Simon Busch
2011-10-12 19:29               ` Simon Busch
2011-10-12 19:52                 ` Simon Busch [this message]
2011-10-12 20:09                   ` Eric Bénard
2011-10-12 19:41               ` Chris Larson
2011-10-12 19:22       ` Eric Bénard
2011-10-12  7:45 ` [oe-core 2/4] qt4-x11-free: bring back pkg-config fixups Martin Jansa
2011-10-12  9:23   ` Paul Eggleton
2011-10-12 18:05     ` Simon Busch
2011-10-19 19:02       ` Simon Busch
2011-10-12  7:45 ` [oe-core 3/4] conf: machine: includes: add armv6-novfp support Martin Jansa
2011-10-12 21:26   ` Phil Blundell
2011-10-13 10:49     ` Denis 'GNUtoo' Carikli
2011-10-13 19:42       ` Phil Blundell
2011-12-21 19:48         ` [PATCH] " vquicksilver
2011-12-21 19:57           ` Mark Hatle
2011-12-21 20:06           ` Otavio Salvador
2011-12-21 20:12             ` Koen Kooi
2011-12-21 22:16         ` [PATCH v2] " Víctor Enríquez
2011-12-27 19:02           ` Saul Wold
2011-10-12  7:45 ` [oe-core 4/4] xserver-xorg: drop xorg-minimal-fonts from RDEPENDS Martin Jansa

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=4E95EFEB.6040204@gravedo.de \
    --to=morphis@gravedo.de \
    --cc=openembedded-core@lists.openembedded.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