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@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