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 20:34:56 +0200 [thread overview]
Message-ID: <4E95DDD0.7020302@gravedo.de> (raw)
In-Reply-To: <1E1E70C9-6B15-497F-8571-78D2EF0CD081@dominion.thruhere.net>
On 12.10.2011 20:14, Koen Kooi wrote:
>
>
> Op 12 okt. 2011 om 20:10 heeft Simon Busch <morphis@gravedo.de> het volgende geschreven:
>
>> On 12.10.2011 10:02, Eric Bénard wrote:
>>> Hi,
>>>
>>> Le 12/10/2011 09:45, Martin Jansa a écrit :
>>>> From: Simon Busch<morphis@gravedo.de>
>>>>
>>>> In most cases we don't need tslib in std. configuration as touchscreen
>>>> access in most
>>>> devices today is done with linux input interface. If some specific
>>>> machine has a need for
>>>> tslib support it should add the dependency in it's machine layer again
>>>> and modify the
>>>> profile script accordingly.
>>>>
>>> When using a resistive touchscreen, tslib is a common solution to handle
>>> calibration and raw value processing : do you think this is a good thing
>>> to remove this ?
>>
>> Thats up to the environment you are using qt4-embedded in. In my case
>> the setup is a little bit more complicated. We're using tslib but not
>> directly in qt4-embedded (we can get rid of tslib completely but time is
>> missing).
>>
>> I removed the dependency from qt4-embedded as qt4-embedded in oe-core
>> should be the general thing used in all environments and therefore
>> should be only a minimal setup with minimal dependencies.
>
> No, it should work in most cases, breaking qt:e like is not acceptable.
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).
--
Simon Busch - http://mm.gravedo.de/blog/
next prev parent reply other threads:[~2011-10-12 18:40 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 [this message]
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
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=4E95DDD0.7020302@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