From: Keith Kyzivat <kamaji@gmail.com>
To: meta-ti@yoctoproject.org
Subject: Re: Rename of omap5-sgx-ddk-um-linux to ti-sgx-ddk-um not complete?
Date: Tue, 24 May 2016 14:48:01 +0000 [thread overview]
Message-ID: <CAH5ySaex5z7G1rKpkXgpnOMnPkFYkL3xQrTp3ZWOcg0jqU_0wQ@mail.gmail.com> (raw)
In-Reply-To: <CAH5ySac1VscW4vszpXbj4zw5vDZhCovVyxtnLKn59k=8JjVp5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2710 bytes --]
next prev parent reply other threads:[~2016-05-24 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 23:41 Rename of omap5-sgx-ddk-um-linux to ti-sgx-ddk-um not complete? Keith Kyzivat
2016-05-20 20:50 ` Denys Dmytriyenko
2016-05-24 14:48 ` Keith Kyzivat [this message]
[not found] ` <371273705.3403881.1464113612415.JavaMail.yahoo@mail.yahoo.com>
2016-05-24 18:21 ` Benjamin Bimmermann
2016-05-25 15:20 ` Keith Kyzivat
2016-05-25 21:24 ` Benjamin Bimmermann
2016-06-06 22:38 ` Keith Kyzivat
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=CAH5ySaex5z7G1rKpkXgpnOMnPkFYkL3xQrTp3ZWOcg0jqU_0wQ@mail.gmail.com \
--to=kamaji@gmail.com \
--cc=meta-ti@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.