All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luca" <magnabosco.luca@gmail.com>
To: meta-ti@lists.yoctoproject.org
Subject: Build core-image-weston for beaglebone/am335x with GPU SGX530 enabled
Date: Mon, 11 May 2020 08:07:49 -0700	[thread overview]
Message-ID: <zrPI.1589209669954801158.UpYg@lists.yoctoproject.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3159 bytes --]

Hi all,

I am trying to get Weston working with the GPU SGX530 enabled.
Basically I would like to get the same results described in BeagleBoneBlack/SGX + Qt EGLFS + Weston ( https://elinux.org/BeagleBoneBlack/SGX_%2B_Qt_EGLFS_%2B_Weston ) using Yocto.

At the moment I am using:

* meta-ti: branch zeus, commit 1dd4558 (with a fixed .wks see https://lists.yoctoproject.org/g/meta-ti/message/12916). I will probably switch to tag ti2020.00 or previous if needed
* poky: branch zeus, commit ca9cc50
* meta-openembedded: branch zeus, commit 44e458f
* A very simple patch applied by a ti-sgx-ddk-km_%.bbappend to set "$(1)_compiler_preferred_target := arm-linux-gnueabihf" when arm-poky-linux-gnueabi is used (Similar to the patch described in https://www.yoctoproject.org/pipermail/meta-ti/2019-September/012193.html but with arm-poky-linux-gnueabi instead of arm-oe-linux-gnueabi ).

The board seems to boot properly if I use core-image-base but when I run bitbake core-image-weston I get some bitbake errors due to libgl.

*First approach*
In my local.conf

IMAGE_INSTALL_append = " ti-sgx-ddk-km ti-sgx-ddk-um libdrm"
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_virtual/mesa = "ti-sgx-ddk-um"

After taking a look to https://code.qt.io/cgit/yocto/meta-boot2qt.git meta-ti-extras layer dropped with commit 17747110065d6d1482fb5786773c27d78f7c8bac I added in my ti-sgx-ddk-um_%.bbappend

PROVIDES += "virtual/mesa"

Anyway when I run bitbake core-image-weston, it stops immediately with the error:
Nothing PROVIDES 'virtual/libgl' (but /home/qem/Yocto/poky-zeus/meta/recipes-graphics/clutter/clutter-1.0_1.26.2.bb, /home/qem/Yocto/poky-zeus/meta/recipes-graphics/cairo/cairo_1.16.0.bb, /home/qem/Yocto/poky-zeus/meta/recipes-graphics/libepoxy/libepoxy_1.5.3.bb DEPENDS on or otherwise requires it)
mesa-gl PROVIDES virtual/libgl but was skipped: PREFERRED_PROVIDER_virtual/libgl set to mesa, not mesa-gl
mesa PROVIDES virtual/libgl but was skipped: PREFERRED_PROVIDER_virtual/libgles1 set to ti-sgx-ddk-um, not mesa

*Second approach*
Considering https://www.yoctoproject.org/pipermail/meta-ti/2016-October/009100.html I deleted the  In my ti-sgx-ddk-um_%.bbappend and modified my local.conf setting

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"

But bitbake stops with the same error of the first approach.

*Doubts about Weston and OpenGL*
Looking for a solution I sow https://patchwork.openembedded.org/patch/152082/ and http://git.yoctoproject.org/cgit/cgit.cgi/meta-freescale/tree/recipes-graphics/wayland/weston_4.0.0.imx.bb?h=thud and I am wondering if "REQUIRED_DISTRO_FEATURES = "opengl"" is strictly required for Weston 7 or if a solution similar to the one implemented for Weston 4 would be viable.

Any suggestion or consideration would be much appreciated

Regards

Luca

[-- Attachment #2: Type: text/html, Size: 4706 bytes --]

             reply	other threads:[~2020-05-11 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 15:07 Luca [this message]
2020-05-17 21:22 ` Build core-image-weston for beaglebone/am335x with GPU SGX530 enabled Luca
2020-05-18 18:03   ` [meta-ti] " Andrew F. Davis
2020-05-18 19:19     ` Luca
2020-05-18 19:30       ` [meta-ti] " Denys Dmytriyenko
2020-05-19  8:04         ` Luca

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=zrPI.1589209669954801158.UpYg@lists.yoctoproject.org \
    --to=magnabosco.luca@gmail.com \
    --cc=meta-ti@lists.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.