From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-core@lists.openembedded.org
Subject: mesa, libgbm and weston
Date: Thu, 21 Apr 2016 20:05:19 -0400 [thread overview]
Message-ID: <20160422000519.GR16135@denix.org> (raw)
All,
I've been meaning to ask this for quite some time. It appears that Weston's
DRM compositor enabled with "kms" PACKAGECONFIG doesn't really need the entire
mesa, but it only needs libgbm. Now, mesa in OE-Core provides libgbm as one of
its packages, hence virtual/mesa is added in DEPENDS for kms:
PACKAGECONFIG[kms] = "--enable-drm-compositor,--disable-drm-compositor,drm udev virtual/mesa mtdev"
On TI platforms with SGX GPU we have GLES/EGL stack (provided by proprietary
blobs, yeah) and a separate libgbm, based on Rob Clark's https://github.com/robclark/libgbm
Since that is enough to run Weston on our platforms, I've been carrying this
bbappend for long time:
PACKAGECONFIG[kms] = "--enable-drm-compositor,--disable-drm-compositor,drm udev libgbm mtdev"
It's been working fine for long time, but people keep on asking questions and
require cleaner solution, since bbappend in a separate layer is somewhat
confusing. Now, the question is what is a proper solution here:
1. Change weston recipe in oe-core to depend on libgbm instead of virtual/mesa
assuming that it is provided by mesa recipe and it works for other platforms.
2. Change our libgbm recipe to declare that it PROVIDES virtual/mesa, although
it looks like a hack and is somewhat reverse...
--
Denys
next reply other threads:[~2016-04-22 0:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 0:05 Denys Dmytriyenko [this message]
2016-04-22 0:27 ` mesa, libgbm and weston Christopher Larson
2016-04-25 16:50 ` Denys Dmytriyenko
2016-04-26 11:59 ` Burton, Ross
2016-04-26 14:00 ` Burton, Ross
2016-04-26 14:27 ` Denys Dmytriyenko
2016-04-26 14:49 ` Otavio Salvador
2016-04-26 14:05 ` Denys Dmytriyenko
2016-04-26 11:36 ` Burton, Ross
2016-04-26 14:02 ` Denys Dmytriyenko
2016-04-26 19:06 ` Burton, Ross
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=20160422000519.GR16135@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox