From: "Mark Hatle" <mark.hatle@kernel.crashing.org>
To: "Adrian Bunk" <bunk@stusta.de>
Cc: "Mark Hatle" <mark.hatle@kernel.crashing.org>,
"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 09:15:58 -0500 (CDT) [thread overview]
Message-ID: <58432.149.199.62.130.1585232158.squirrel@gate.crashing.org> (raw)
In-Reply-To: <20200326131141.GB17705@localhost>
> 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"
> ?
I don't know. I didn't write this.
However, doing some investigation, the big difference here is the overall
capabilities. There are common distributions where a user may want to use
mesa (no external libdrm) as well as distress where they want to use an
external drm and the mesa-gl version only.
So 'mesa' and 'external drm + mesa-gl' are equivalent in functionality for
a given distro. Only difference being optimization.
You may ask why would I use one vs the other. In my case, we have a
family of SoC parts. Some of the family have a Mali graphics chip on
them, while others don't have any optimized graphics so everything has to
be software rendered. The only difference (from a software point of view)
is if the Mali is on-board or not. So using a common (binary)
distribution, and being able to just swap those parts is highly desirable.
(Does that ACTUALLY work right now, I'm not sure.. but that is what I am
working on.)
>> --Mark
>
> cu
> Adrian
>
next prev parent reply other threads:[~2020-03-26 14:16 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
2020-03-26 14:15 ` Mark Hatle [this message]
[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=58432.149.199.62.130.1585232158.squirrel@gate.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=alex.kanavin@gmail.com \
--cc=bunk@stusta.de \
--cc=denis@denix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox