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: Fri, 17 Dec 2021 11:15:58 +0100 [thread overview]
Message-ID: <89da716e-cb91-4d1d-7bd3-07aa90d8b8cc@arachnodroid.de> (raw)
In-Reply-To: <1084ea3f-802f-d24b-f613-7bc74c7a1800@mind.be>
Hi!
I've applied the patch to the latest origin/master. One hunk has been
rejected:
--- package/mesa3d/Config.in
+++ package/mesa3d/Config.in
@@ -70,6 +75,8 @@ config BR2_PACKAGE_MESA3D_DRI_DRIVER
!BR2_PACKAGE_MESA3D_OPENGL_GLX && \
!BR2_PACKAGE_MESA3D_OPENGL_EGL && \
!BR2_PACKAGE_MESA3D_OSMESA_GALLIUM
+ select BR2_PACKAGE_MESA3D_DRI3 if \
+ (BR2_PACKAGE_XORG7 && BR2_TOOLCHAIN_HAS_SYNC_4)
select BR2_PACKAGE_XLIB_LIBXSHMFENCE if \
(BR2_PACKAGE_XORG7 && BR2_TOOLCHAIN_HAS_SYNC_4)
But it looks good for me anyway. I've tried by using
raspberrypi_64_defconfig and only enabled mesa3d with Gallium drivers
for V3D and VC4.
According to the build log, it has been compiled with DRI3 support.
Regards,
Michael
Am 12/16/21 um 7:33 PM schrieb Arnout Vandecappelle:
>
>
> On 16/12/2021 19:12, Bernd Kuhls wrote:
>> Am Thu, 16 Dec 2021 18:28:56 +0100 schrieb Arnout Vandecappelle:
>>
>>> Bernd, can you comment?
>>
>> Hi Arnout,
>>
>> no, because I do not use buildroot on rbpi hardware.
>>
>> But the topic was already discussed this summer, with no solution afaics:
>> https://patchwork.ozlabs.org/project/buildroot/list/?
>> series=248555&submitter=&state=*&q=&archive=&delegate=
>
> Good find, thanks!
>
> Michael, can you try that patch [1] and see if it works for you?
>
> Peter, I think I'm just going to apply []] except that I'll make
> BR2_PACKAGE_MESA3D_DRI3 a blind option (i.e. not user visible, only
> selected automatically by the drivers, much like BR2_PACKAGE_MESA3D_DRI).
>
> My other major comment about that patch was that I suspected that it
> would need some 'select' statements, but I guess the autobuilders will
> inform us of that, so we can go ahead and merge it.
>
> Does that sound OK to you?
>
> Regards,
> Arnout
>
>
> [1]
> https://patchwork.ozlabs.org/project/buildroot/patch/20210612223011.26118-1-ps.report@gmx.net/
>
>
>
>>
>> Regards, Bernd
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot@buildroot.org
>> https://lists.buildroot.org/mailman/listinfo/buildroot
>>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-17 10:16 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
[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 [this message]
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=89da716e-cb91-4d1d-7bd3-07aa90d8b8cc@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.