Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with Touchscreen on ARM
Date: Wed, 24 Jun 2015 23:18:05 +0200	[thread overview]
Message-ID: <558B1E8D.9010106@mind.be> (raw)
In-Reply-To: <CALW-xeqpfVVYeff9+RPfhOhEEW3mohbqXEweXP7YQJuoYX1Erg@mail.gmail.com>

On 06/24/15 16:23, Guillaume s?tan wrote:
> Hello,
> 
> I try to use a Touchscreen (multitouch) with my target (Arm Little endian -
> Cortex - A9 ).
> I tried to use EFL, directfb and fb but I haven't managed to run the multitouch
> on my target.

 fb is just a framebuffer driver so doesn't have a relation with input events.

 directfb doesn't yet support multitouch AFAIK.

 EFL should support multitouch. But I guess you have to configure it to listen
to the right input device.

> 
> Please can you explain me what packages are needed to use multitouch ?
> Or have you ever used a touch screen on a target Arm ?

 You could try tslib (which converts multitouch to single touch so probably not
really what you want). Qt5 also has support for multitouch.

> 
> Regards,
> 
> Guillaumme 
> 
> 
> PS : I see frames on my target (arm ) when I touch my screen with application mtdev.

 What do you mean with 'frames'?


 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-06-24 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 14:23 [Buildroot] Problem with Touchscreen on ARM Guillaume sétan
2015-06-24 21:18 ` Arnout Vandecappelle [this message]
2015-06-25  8:04   ` Guillaume sétan
2015-06-25 23:08     ` Arnout Vandecappelle

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=558B1E8D.9010106@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.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