From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] RFC: meta-oe appends and overlayed recipes
Date: Tue, 12 Feb 2013 22:22:55 +0100 [thread overview]
Message-ID: <20130212212255.GF3300@jama> (raw)
In-Reply-To: <CAJTo0LYFcT5P=p62Nn2kBak33LCfBXQ_KFL-oF2bHFKhguk1rg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
On Tue, Feb 12, 2013 at 08:51:25PM +0000, Burton, Ross wrote:
> On 12 February 2013 16:43, Otavio Salvador <otavio@ossystems.com.br> wrote:
> >> Qt Embedded as we build it is currently configured to use tslib, as is
> >> SDL. If the alternative (evdev?) is supported they could presumably be
> >> switched over though. I don't know how practical that is however.
> >
> > Yes Qt Embedded uses it; not sure evdev is an alternative here.
>
> I'd be surprised if QtE doesn't support evdev, but I've been surprised
> a lot recently. Can you investigate quickly to see if QtE supports
> evdev?
>
> As far as X and oe-core is concerned, tslib isn't involve at all
> anymore. There are xorg-input-tslib drivers in Debian but they've not
> been touched for years, the upstream source URL doesn't exist any
> more, and I'd actually be somewhat surprised if they worked. Xorg is
> all about evdev + xinput for touchscreens.
Yes, xf86-input-tslib works
http://git.openembedded.org/meta-openembedded/commit/?id=506d5f781f5ee93e3c9b8ca51a7fb65f40d4a8b8
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-02-12 21:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 17:09 RFC: meta-oe appends and overlayed recipes Paul Eggleton
2013-02-11 17:50 ` Otavio Salvador
2013-02-12 8:38 ` Anders Darander
2013-02-11 22:35 ` Richard Purdie
2013-02-12 9:24 ` Paul Eggleton
2013-02-12 13:10 ` Richard Purdie
2013-02-12 13:38 ` Paul Eggleton
2013-02-12 10:24 ` [oe] " Burton, Ross
2013-02-12 10:38 ` Paul Eggleton
2013-02-12 16:43 ` Otavio Salvador
2013-02-12 20:51 ` Burton, Ross
2013-02-12 21:22 ` Martin Jansa [this message]
2013-02-12 21:36 ` Burton, Ross
2013-02-12 21:40 ` Otavio Salvador
2013-02-12 21:53 ` Eric Bénard
2013-02-12 22:02 ` Burton, Ross
2013-02-12 15:50 ` Ross Burton
2013-02-12 16:44 ` Otavio Salvador
2013-02-12 16:53 ` Paul Eggleton
2013-02-12 19:19 ` Martin Jansa
2013-02-12 19:31 ` [oe] " Otavio Salvador
2013-02-12 19:32 ` Paul Eggleton
2013-02-12 19:51 ` Martin Jansa
2013-02-12 20:40 ` Marcin Juszkiewicz
2013-02-12 19:32 ` [oe] " Chris Larson
2013-02-12 19:59 ` Mark Hatle
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=20130212212255.GF3300@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@linux.intel.com \
--cc=ross.burton@intel.com \
/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