All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Wilson-Lindberg <GWilson@sakuraus.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: virtual/egl on Raspberry Pi 4
Date: Mon, 4 Oct 2021 19:39:04 +0000	[thread overview]
Message-ID: <0c6e789aba8141509bb31779a8393cbf@sakuraus.com> (raw)

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

Hello list,

I'm working on a Qt supplied boot2qt Yocto build currently based on Zeus that is running on a Raspberry Pi 4. I recently updated the qt version to 5.15.6 and Qt changed something in the Yocto configuration that they are using and now one of the recipes that we use is failing saying that in needs 'virtual/egl' but that it is not provided by any recipe.



In the searching that I have done I have found that the raspberry pi 4 is particular on which package supplies the virtual/egl but I haven't seen anything that indicates what I should do to re-enable it.



Can anyone tell me what I need to do to enable the correct driver to get virtual/egl provided on the Raspberry Pi 4? Or maybe even better, how I could search through the packages that are enabled on the old and new Yocto trees so that I can figure out what changed between the releases and re-enable the virtual/egl.



Best Regards,

Greg Wilson-Lindberg


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

             reply	other threads:[~2021-10-04 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 19:39 Greg Wilson-Lindberg [this message]
2021-10-04 21:17 ` [yocto] virtual/egl on Raspberry Pi 4 Khem Raj
2021-10-04 23:08   ` Greg Wilson-Lindberg
2021-10-05  0:14     ` Khem Raj
2021-10-05 15:53       ` Greg Wilson-Lindberg
2021-10-05 16:31         ` Khem Raj
2021-10-05 18:22           ` Greg Wilson-Lindberg
2021-10-06 11:26             ` Joel Winarske
2021-10-06 17:01               ` Greg Wilson-Lindberg

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=0c6e789aba8141509bb31779a8393cbf@sakuraus.com \
    --to=gwilson@sakuraus.com \
    --cc=yocto@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.