All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Filip Piechocki <fpiechocki@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm] QT5 on SabreLite
Date: Fri, 24 Jan 2014 12:57:00 -0700	[thread overview]
Message-ID: <52E2C58C.2080104@mlbassoc.com> (raw)
In-Reply-To: <CAALoMC2cK--FjjG-dZcORD9LsfGv79+h=GEkYfH2AiA4Bt9PZw@mail.gmail.com>

On 2014-01-24 11:35, Filip Piechocki wrote:
> Hi,
>
> Maybe try different device (e.g. /dev/input/event0). AFAIR it should be like this for example:
>
> ... -plugin tslib:/dev/input/event0
>
> or instead of adding this as command line argument it can be set as environment variable:
>
> export QT_QPA_GENERIC_PLUGINS=tslib:/dev/input/event0

Yes, that fixed it, thanks.  I used tslib:/dev/input/touchscreen0

> On Fri, Jan 24, 2014 at 6:13 PM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
>     I finally got QT5 to build for my i.MX6Q SabreLite.  I'm able
>     to run the cinematic demo, but the touch screen isn't working.
>     Here's what I get:
>
>     root@sabrelite:~# Qt5_CinematicExperience -platform eglfs -plugin tslib
>     evdevtouch: Using device /dev/input/event1
>     min X: 0 max X: 0
>     min Y: 0 max Y: 0
>     min pressure: 0 max pressure: 4095
>     device name: tsc2004
>     EGLFS: Unable to query physical screen size, defaulting to 100 dpi.
>     EGLFS: To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).
>     QTsLibMouseHandler "tslib" ""
>     Protocol type A
>     libpng warning: iCCP: known incorrect sRGB profile
>     libpng warning: iCCP: known incorrect sRGB profile
>
>     Notice that the touch window is 0x0.  I know the touch is set up
>     properly and calibrated as I've run the ts_* programs as well as
>     X11 and QT4.
>
>     How do I get the touch screen working with QT5?
>
>     BTW, the demo reports being able to display a screaming 177FPS!
>     Does that make sense?
>
>     --
>     ------------------------------__------------------------------
>     Gary Thomas                 |  Consulting for the
>     MLB Associates              |    Embedded world
>     ------------------------------__------------------------------
>     _________________________________________________
>     meta-freescale mailing list
>     meta-freescale@yoctoproject.__org <mailto:meta-freescale@yoctoproject.org>
>     https://lists.yoctoproject.__org/listinfo/meta-freescale <https://lists.yoctoproject.org/listinfo/meta-freescale>
>
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      parent reply	other threads:[~2014-01-24 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 17:13 [meta-fsl-arm] QT5 on SabreLite Gary Thomas
2014-01-24 17:38 ` Eric Bénard
2014-01-24 17:50   ` Gary Thomas
2014-01-24 18:35 ` Filip Piechocki
2014-01-24 19:28   ` dora 3.10.9 w/fsl-image-gui? randy.krakora
2014-01-24 19:32     ` Fabio Estevam
2014-01-24 19:44       ` randy.krakora
2014-01-24 19:57   ` Gary Thomas [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=52E2C58C.2080104@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=fpiechocki@gmail.com \
    --cc=meta-freescale@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.