[meta-ti] Rename of omap5-sgx-ddk-um-linux to ti-sgx-ddk-um not complete?

Mon Jun 6 15:38:33 PDT 2016

Hi Benjamin,

SGX: -- isn't this already enabled from
meta-ti/conf/machine/include/ti33x.inc, included by
meta-ti/conf/machine/beaglebone.conf ?:  MACHINE_FEATURES = "kernel26 apm
usbgadget usbhost vfat ext2 screen alsa ethernet sgx"

You must be referring to going the approach of using the jumpnowtek
meta-bbb layer that doesn't use meta-ti.  I've been sticking with
meta-embarcados for the time being - pulling what I can from their master
branch, and adapting it to work with the krogoth branch...  I might jump
entirely free of it though and just depend on meta-ti and meta-qt.. for the
moment it works ok for me.

I see the cleanup you referenced -- haven't tried yet to remove it, but
makes sense - it's referring to the old outdated/incorrect omap driver.

As for improving performance- just today I pulled latest changes from
meta-ti and Qt5_CinematicExperience is working well for me now, when before
it wasn't operating at all.  I think the commit that fixes the issue is
: 2a57c4c ti-sgx-ddk-um: update srcrev and bump PR
This commit pulls a newer rev of the kernel graphics module.

Fonts are also fixed now -- previously I found that, while fontconfig was
built, and fonts were placed on the system, none were loaded when my Qt app
ran, and thus text fields, buttons, etc were devoid of text.  I'm not
entirely sure what fixed the font issue -- as I have made a few changes to
my local.conf that are fontconfig related, but none seemed to correct the
issue until I did a full rebuild (wiping the tmp dir but keeping same
sstate dir) - which I did when I pulled the latest meta-ti changes.

Something I can't figure out - that I had working at one point, but no
longer have working is setting the default platform plugin to 'eglfs'
instead of 'xcb' (which isn't even built!).
My guess is I'm using a var that isn't used in krogoth, that was used in
fido:
EXTRA_OECONF_append = " -qpa eglfs" in one of  my qtbase_%.bbappend files.

Anyway! Try a rebuild with latest meta-ti, and I think you'll find better
graphics performance in QML-based applications.

~Keith

On Wed, May 25, 2016 at 5:24 PM Benjamin Bimmermann <b.bimmermann at yahoo.de>
wrote:

> Hello,
>
> first it is good to share informations so maybe the meta-ti devs can fix
> this.
>
> Now to you:
> I think you are at a ponit where I was about 2 mounth ago. So I will help
> you if you share later a fix for the Qt5_CinematicExperience.
>
> First:
> I think you try to use:
> http://www.embarcados.com.br/beaglebone-black-qt5-yocto-parte-1/
> I think this is to old. You should more fokus and use:
> http://www.jumpnowtek.com/
> https://github.com/jumpnow/meta-bbb
>
> The Problem with the jumpnow layer is that they don't use the meta-ti
> layer. So they can not build very good and fast qt5 aps.
>
> Second:
>
> What you don't need I think :
> /home/vagrant/yocto/poky/meta-embarcados \
> RDEPENDS_packagegroup-qt5-machine-related = "\ -
> ${@base_contains('MACHINE', 'beaglebone', 'libgles-omap3
> omap3-sgx-modules', '', d)} \ + ${@base_contains('MACHINE', 'beaglebone',
> 'omap5-sgx-ddk-um-linux', '', d)} \ "
>
>
> ----------------------------------------------------------------------------
>
> Third:
>
> You must enable SGX in your system and overlay !!!
>
> Four :
>
> I have better experience with:
> beaglebone.conf:
>     require conf/machine/include/ti33x.inc
>     require conf/machine/include/THE_arago-prefs.inc
>     UBOOT_MACHINE = "am335x_boneblack_config"
>     MACHINE_FEATURES += " serial usbhost sgx "
>     PREFERRED_PROVIDER* (like the last e-mail)
>
> Image:
>
> IMAGE_INSTALL += " \
>     ti-sgx-ddk-um \    omapdrm-pvr \
>    packagegroup-qt5-toolchain-target \   qtmultimedia \   qtmultimedia-dev \   qtmultimedia-mkspecs \ "
>
>   local.conf:
>
> PACKAGECONFIG_GL_pn-qtbase = "gles2"PACKAGECONFIG_GL_append += " accessibility examples gles2 libs tools"PACKAGECONFIG_append_pn-qtmultimedia = " gstreamer"DISTRO_FEATURES_append = " opengl usbhost sgx"DISTRO_FEATURES_remove = " x11  "
> RM_OLD_IMAGE = "1"
> EXTRA_IMAGE_FEATURES = "debug-tweaks tools-debug ssh-server-openssh"
>
>
> I hope I could help and maybe we find a solution for the problem and add
> this to meta-ti.
>
> Have a nice day.
>
>
>
> Keith Kyzivat <kamaji at gmail.com> schrieb am 17:20 Mittwoch, 25.Mai 2016:
>
>
>
>
> Hi Benjamin,
>
> Thank you for your config details -- that's gotten me further -- with a
> working driver, and Qt5_CinematicExperience actually running, bringing up
> the initial display, cursor showing, and the opening "Curtains" display,
> but sounds like a similar experience to what you're describing -- driver
> starting, program starting, but dreadful performance to the point where it
> doesn't really get beyond the first frame, and emits many FIFO underflow
> messages.  DMA may be not enabled or is somehow failing?
>
> In any case, I'm further, and will continue to research the issue and hack
> away.  I'll report any progress.
> Should I keep it off-list, or is it on-topic enough for this mailing list?
>
> Anyone have any pointers to what the issue might be?
>
> Qt5_CinematicExperience output log:
> https://gist.github.com/keithel/e4eaf0a44aaa5d060f0578345d05b9b3#file-qt5_cinematicexperience-output
>
> You can also find my config in that gist.
>
> ~Keith
>
> On Tue, May 24, 2016 at 2:21 PM Benjamin Bimmermann <b.bimmermann at yahoo.de>
> wrote:
>
> Hello,
>
> I build with Krogoth a QT5.6 Image.
> I have Include in my Image:
>
> IMAGE_INSTALL += " \    ti-sgx-ddk-um \    omapdrm-pvr \"
>
> and the config :
> PREFERRED_PROVIDER_virtual/libgl = "mesa-gl"PREFERRED_PROVIDER_virtual/mesa = "mesa-gl"
> PREFERRED_PROVIDER_virtual/egl_keystone = "mesa"PREFERRED_PROVIDER_virtual/libgles1_keystone = "mesa"PREFERRED_PROVIDER_virtual/libgles2_keystone = "mesa"
> PREFERRED_PROVIDER_virtual/libgl_keystone = "mesa"PREFERRED_PROVIDER_virtual/mesa_keystone = "mesa"
> PREFERRED_PROVIDER_virtual/kernel = "linux-ti-staging"PREFERRED_VERSION_linux-ti-staging = "4.4%"
> PREFERRED_PROVIDER_virtual/egl = "ti-sgx-ddk-um"PREFERRED_PROVIDER_virtual/libgles1 = "ti-sgx-ddk-um"PREFERRED_PROVIDER_virtual/libgles2 = "ti-sgx-ddk-um"PREFERRED_PROVIDER_libgbm = "libgbm"PREFERRED_PROVIDER_libgbm-dev = "libgbm-dev"
>
>
> This Image works Ok. Not great. If you build things like :
> https://github.com/scottellis/tspress
> It works very well. If you try to build big things like:
> https://github.com/rzr/qt5-cinematic-experience
> The driver Starts but and the Programm try to start.
> You see a mouse Courser and thats it. The Programm doesn't run ok.
>
> If you have a solution for that or if we find together for that a solution it would be very nice.
>
> Have a nice day.
>
>
>
>
> Keith Kyzivat <kamaji at gmail.com> schrieb am 16:48 Dienstag, 24.Mai 2016:
>
>
>
>
> Hi Denys,
>
> I'm working with the Beaglebone Black Rev C board -- so AM335x-based.
> What incantation/recipe/package should I be specifying to get the
> userspace DRI drivers for use with libGLESv2 built into my image? That's
> been my biggest stumbling block.  Even moving back to Fido I was unable to
> build an image that includes the userspace graphics support libraries.
>
> Ultimately I want to pull in Qt 5.6 and be able to run QML-based apps with
> the 'eglfs' QPA platform plugin with hardware OpenGLES2 acceleration
> running over HDMI.
>
> Are there any good resources ((e)books, wikis, presentations, etc)  you or
> anyone else can recommend to fully grasp Yocto/OpenEmbedded?  I've come
> across a number of presentations, wikis and blog posts that have explained
> some things, but no comprehensive walkthrough that performs a build and
> explains all the reasons for the changes.
>
> ~Keith
>
> On Thu, May 19, 2016 at 7:41 PM Keith Kyzivat <kamaji at gmail.com> wrote:
>
> Hi folks,
>
> I've been trying to get a beagleboard krogoth build working with working
> OpenGLES2 DRI drivers in place, and have been failing.
>
> I did find out that drivers changed name from libgles-omap3 to
> ti-sgx-ddk-um - but specifying ti-sgx-ddk-um as my
> PREFERRED_PROVIDER_virtual/libgles2 fails hard --
>  -- Nothing RPROVIDES 'ti-sgx-ddk-um'
>
> Digging through commits, I found commit c70102c671 -
> renaming omap5-sgx-ddk-um-linux to ti-sgx-ddk-um.
>
> The problem seems to be that these are renamed, but the package names have
> not changed -- recipes-graphics/libgles/ti-sgx-ddk-um_1.14.3699939.bb
> includes:
>
> PROVIDES += "virtual/egl virtual/libgles1 virtual/libgles2
> omap5-sgx-ddk-um-linux"
>
> Shouldn't this be the following?
> PROVIDES += "virtual/egl virtual/libgles1 virtual/libgles2 ti-sgx-ddk-um"
>
> And also RPROVIDES, RREPLACES, RCONFLICTS and associated -dev, -dbg
> packages?
>
> Apologies if I'm asking this wrong - I'm pretty new to Yocto/OE and still
> figuring it all out.
>
> ~Keith Kyzivat
>
>
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20160606/94265f97/attachment-0001.html>