All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Taubert <info@arachnodroid.de>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/mesa3d: don't disable DRI3 for some Gallium drivers
Date: Thu, 16 Dec 2021 19:26:03 +0100	[thread overview]
Message-ID: <575adfc5-e3e1-1bfd-f40d-73d5caa189f5@arachnodroid.de> (raw)
In-Reply-To: <aafcded5-c0f4-4745-a226-da57d0e7a805@mind.be>

Hi Arnout,

I'm not that familiar with these configs, yet. But if I understand it 
right, your advice is to have the selection of these Gallium drivers 
should also select BR2_PACKAGE_MESA3D_DRI_DRIVER.

I will have a look on how to do that tomorrow and provide another patch 
then.

Kind regards,
Michael

Am 16.12.2021 um 18:28 schrieb Arnout Vandecappelle:
>   Hi Michael,
> 
> On 14/12/2021 20:06, Michael Taubert wrote:
>> Certain Gallium drivers need DRI3 support, otherwise opengl won't work.
>> On the Raspberry Pi 4, for example, glxgears will complain about
>>
>> 'Failed to open bo 1: permission denied'
>>
>> These drivers must not be selected to disable DRI3 support. It seems to
>> be the same for Lima and Panfrost, please check bug 13831.
>>
>> Signed-off-by: Michael Taubert <info@arachnodroid.de>
>> ---
>>   package/mesa3d/mesa3d.mk | 6 +++++-
>>   1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/package/mesa3d/mesa3d.mk b/package/mesa3d/mesa3d.mk
>> index 61b095ccca..9780d5a960 100644
>> --- a/package/mesa3d/mesa3d.mk
>> +++ b/package/mesa3d/mesa3d.mk
>> @@ -121,7 +121,11 @@ MESA3D_CONF_OPTS += \
>>          -Dgallium-extra-hud=true
>>   endif
>>
>> -ifeq ($(BR2_PACKAGE_MESA3D_DRI_DRIVER),)
>> +ifeq ($(BR2_PACKAGE_MESA3D_DRI_DRIVER) \
>> +       $(BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_V3D) \
>> +       $(BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_VC4) \
>> +       $(BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_LIMA) \
>> +       $(BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_PANFROST),)
> 
>   The mesa3d stuff goes way over my head, actually, but I would think 
> that the proper solution here would be that these configs select 
> BR2_PACKAGE_MESA3D_DRI_DRIVER.
> 
>   I know it sounds weird that a gallium driver is also a DRI driver, but 
> I guess that's what it is...
> 
>   Bernd, can you comment?
> 
>   Regards,
>   Arnout
> 
>>   MESA3D_CONF_OPTS += \
>>          -Ddri-drivers= -Ddri3=disabled
>>   else
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-12-16 18:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 10:00 [Buildroot] [Bug 14451] New: nodejs won't build on Fedora 35 bugzilla
2021-12-13 16:27 ` [Buildroot] [Bug 14451] " bugzilla
2021-12-14 19:03 ` bugzilla
2021-12-14 19:06   ` [Buildroot] [PATCH 1/1] package/mesa3d: don't disable DRI3 for some Gallium drivers Michael Taubert
2021-12-16 17:28     ` Arnout Vandecappelle
2021-12-16 18:26       ` Michael Taubert [this message]
     [not found]     ` <aafcded5-c0f4-4745-a226-da57d0e7a805__41403.4441857197$1639675757$gmane$org@mind.be>
2021-12-16 18:12       ` Bernd Kuhls
2021-12-16 18:33         ` Arnout Vandecappelle
2021-12-16 21:45           ` Peter Seiderer
2021-12-17 10:15           ` Michael Taubert
2021-12-22 14:10 ` [Buildroot] [Bug 14451] nodejs won't build on Fedora 35 bugzilla
2022-01-09 16:28 ` bugzilla

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=575adfc5-e3e1-1bfd-f40d-73d5caa189f5@arachnodroid.de \
    --to=info@arachnodroid.de \
    --cc=buildroot@buildroot.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.