From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Ross Burton <ross.burton@arm.com>
Cc: Khem Raj <raj.khem@gmail.com>, Kai Kang <kai.kang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] mesa: Add native patch via a variable
Date: Wed, 26 Oct 2022 09:34:11 -0500 [thread overview]
Message-ID: <78322791-72e6-75fd-f870-1f2eb7d8e4f6@kernel.crashing.org> (raw)
In-Reply-To: <CANNYZj89RTk6=-tqK550uDvUb3nZ1bfR=H1=Ns2pw5WaiPZ_Tw@mail.gmail.com>
On 10/19/22 5:35 AM, Alexander Kanavin wrote:
> This also begs the question if mesa-gl is actually used by anyone, and
> what warrants its continued inclusion in core as opposed to
> product/BSP layers. I'll propose dropping the recipe and merging .inc
> into mesa.bb once patches start flowing.
>
> The original commit was:
> https://git.yoctoproject.org/poky/commit/?h=master-next&id=015cb13
(I just saw this, so a little late on the reply, but..)
mesa-gl is ABSOLUTELY still being used. It's needed for libmali usage. Not
everyone wants to use lima support for graphics.
It was broken into two separate packages so that is was VERY clear if you were
using mesa for 'everything' (mesa), or mesa JUST for 'gl' (not gles).
--Mark
> Alex
>
> On Wed, 19 Oct 2022 at 08:54, Alexander Kanavin via
> lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
> wrote:
>>
>> On Wed, 19 Oct 2022 at 08:34, Khem Raj <raj.khem@gmail.com> wrote:
>>>
>>> On Tue, Oct 18, 2022 at 10:42 PM Alexander Kanavin
>>> <alex.kanavin@gmail.com> wrote:
>>>>
>>>> Can you show examples where this is needed? Custom variable does not seem a good idea. I also worry that it’ll break automated updates (it’s bad enough with mesa-gl, this might make it worse).
>>>
>>> https://github.com/ndechesne/meta-qcom/blob/master/recipes-graphics/mesa/mesa_git.bb
>>
>> "require recipes-graphics/mesa/mesa.inc"
>>
>> Using recipe includes across layers like this is not a good idea. It
>> imposes requirements on core to continue providing the .inc, and not
>> doing anything with mesa that can 'break' users of that include.
>>
>> Please make it self-contained.
>>
>> Alex
>>
>>
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#171964): https://lists.openembedded.org/g/openembedded-core/message/171964
>> Mute This Topic: https://lists.openembedded.org/mt/94420106/3616948
>> Group Owner: openembedded-core+owner@lists.openembedded.org
>> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [mark.hatle@kernel.crashing.org]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
next prev parent reply other threads:[~2022-10-26 14:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 23:08 [PATCH v2] mesa: Add native patch via a variable Khem Raj
2022-10-19 5:42 ` [OE-core] " Alexander Kanavin
2022-10-19 6:34 ` Khem Raj
2022-10-19 6:54 ` Alexander Kanavin
2022-10-19 15:04 ` Khem Raj
[not found] ` <171F65F5948858B5.6129@lists.openembedded.org>
2022-10-19 10:35 ` Alexander Kanavin
2022-10-26 14:34 ` Mark Hatle [this message]
2022-10-26 16:03 ` Alexander Kanavin
2022-10-26 17:20 ` Mark Hatle
2022-10-26 17:48 ` Joshua Watt
2022-10-26 18:01 ` Alexander Kanavin
2022-10-27 0:46 ` Mark Hatle
2022-10-28 10:59 ` Alexander Kanavin
2022-10-28 18:01 ` Mark Hatle
2022-10-26 20:58 ` Mark Hatle
2022-10-19 15:29 ` Ross Burton
2022-10-19 16:04 ` Alexander Kanavin
2022-10-26 14:13 ` Richard Purdie
2022-10-19 16:05 ` Martin Jansa
2022-10-21 21:59 ` Khem Raj
[not found] ` <171F61FEE1540458.9064@lists.openembedded.org>
2022-10-19 5:50 ` Alexander Kanavin
2022-10-19 5:55 ` Kai
2022-10-19 5:58 ` Martin Jansa
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=78322791-72e6-75fd-f870-1f2eb7d8e4f6@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=alex.kanavin@gmail.com \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross.burton@arm.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