From: "Adrian Bunk" <bunk@stusta.de>
To: Mark Hatle <mark.hatle@kernel.crashing.org>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
Denys Dmytriyenko <denis@denix.org>,
"Burton, Ross" <ross.burton@intel.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] mesa-gl: The purpose of mesa-gl is to provide for X11 usage
Date: Thu, 26 Mar 2020 15:11:41 +0200 [thread overview]
Message-ID: <20200326131141.GB17705@localhost> (raw)
In-Reply-To: <10720.149.199.62.130.1585164457.squirrel@gate.crashing.org>
On Wed, Mar 25, 2020 at 02:27:37PM -0500, Mark Hatle wrote:
> > To be honest, I would just take the entire recipe out. It's causing
> > trouble
> > during updates, isn't being tested neither for builds nor at runtime, and
> > is supposed to provide some specific configuration which as this
> > discussion
> > makes clear, nobody seems to quite understand.
>
> With the abomination that is libmali (and similar), it is still needed.
> It's the only way to support GL on a primarily GLES compatible system.
>
> The problem is the way they do this seems to be a custom version of
> libdrm, which then conflicts with the mesa version. Thus the issues.
>
> I'm happy to continue testing my particular needs now and the future (thus
> the patch against master.)
>...
Stupid question:
Is
PREFERRED_PROVIDER_virtual/mesa = "mesa-gl"
PREFERRED_PROVIDER_virtual/libgl = "mesa-gl"
equivalent to
PACKAGECONFIG_pn-mesa = "opengl dri x11"
?
> --Mark
cu
Adrian
next prev parent reply other threads:[~2020-03-26 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 18:14 [PATCH] mesa-gl: The purpose of mesa-gl is to provide for X11 usage Mark Hatle
2020-03-25 18:21 ` [OE-core] " Denys Dmytriyenko
2020-03-25 18:41 ` Mark Hatle
2020-03-25 19:04 ` Alexander Kanavin
2020-03-25 19:27 ` Mark Hatle
2020-03-26 13:11 ` Adrian Bunk [this message]
2020-03-26 14:15 ` Mark Hatle
[not found] ` <15FFA02F5F44ED82.23217@lists.openembedded.org>
2020-03-25 19:04 ` Mark Hatle
2020-03-25 20:02 ` Andrey Zhizhikin
2020-03-25 20:35 ` Mark Hatle
2020-03-25 21:37 ` Andrey Zhizhikin
2020-03-25 21:48 ` Denys Dmytriyenko
2020-03-25 21:58 ` Otavio Salvador
2020-03-30 12:07 ` Ross Burton
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=20200326131141.GB17705@localhost \
--to=bunk@stusta.de \
--cc=alex.kanavin@gmail.com \
--cc=denis@denix.org \
--cc=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.