All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Issue with Qt5 and PowerVR drivers
Date: Fri, 28 Jun 2013 16:15:33 +0200	[thread overview]
Message-ID: <20130628161533.2dea9fdf@skate> (raw)
In-Reply-To: <321768C95D21724485BCE784F1BE98473EB5E16F@DBDE04.ent.ti.com>

Hello Prabu,

Thanks for your reply!

On Fri, 28 Jun 2013 14:03:05 +0000, Sundareson, Prabindh wrote:

> Very glad to see the video. What version of Qt5 was used ?

The 5.0.2 version, since 5.1 is still alpha (or beta?), we haven't
integrated it in Buildroot yet.

> Qt5 is quite different from Qt4, and the default eglfs port with the
> TI nullws package is a full-screen implementation, fully rendered
> with OpenGL ES2 (ie, the full screen image is a quad texture, and
> cursor is laid as a texture on top of it).

Hum, what is nullws ?

> However an application is free to generate other sized widgets and
> display them (but there are some issues as I mentioned in the Qt bug
> on eglfs). With other platform (non eglfs) implementations, and with
> a window manager in place, you can get desktop windows. The goal with
> Qt5 is to really get a touchscreen based single-screen device going
> with eglfs. If a real desktop implementation is required, better to
> go with the wayland platform plugin.

I'm not interested by multiple applications, only one application has
to run full-screen, but I'd like to see all the widgets drawn by this
application, which is not the case here.

> /etc/powervr.ini  is still used (that is referred by the GL driver
> internally).  PVR2D based powervr plugin is not used in Qt5 as it
> directly uses OpenGL ES2.  But as mentioned above, that is not the
> reason why you get a full screen view.

Yes, I still have a /etc/powervr.ini, except that it points to the
default pvr2d implementation from the PowerVR drivers (i.e
libpvrPVR2D_FRONTWSEGL.so) instead of pointing to the Qt4 specific QWS
library.

> The eglErrors in the context shown below are pending in my list of
> TODOs, and are really indicative of some of the major issues in the
> current rendering framework in Qt5 relating to eglfs. It is going to
> take some effort to push all the patches upstream.

Ok. But things are still not clear for me: is what I am seeing the
expected result with Qt5 as of today, or should I be able to see the
widgets around the OpenGL Qt logo and bubbles?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-06-28 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 12:37 [Buildroot] Issue with Qt5 and PowerVR drivers Thomas Petazzoni
2013-06-28 14:03 ` Sundareson, Prabindh
2013-06-28 14:15   ` Thomas Petazzoni [this message]
2013-06-28 17:56     ` Sundareson, Prabindh
2013-06-29  8:57       ` Thomas Petazzoni

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=20130628161533.2dea9fdf@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 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.