Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mesa: update to 24.3.1, wayland-protocol updated to 1.38 #1395

Open
wants to merge 1 commit into
base: scarthgap
Choose a base branch
from

Conversation

BassemMohsen
Copy link

Based on PR #1390

Update to latest mesa 24.3.1 release
Fixes DRAM DSI linking to missing library drm-rp1-dsi_dri.so

fixes #1389

Added new dependencies required by msea version update.
Removed DRI3 option as it's now removed from meson build options.
Updated Wayland Protocol to 1.38 as it's minimum required version for mesa 24.3.1
This PR will be completed when 24.3.1 is final official release. For now, I'm leaving it as work of progress to help whoever have issues with RPI5 DSI.

Upgrade to latest official mesa release.

Fixes DRM DSI linking to missing and non exisiting library
drm-rp1-dsi_dri.so on mesa 24.0.7 from poky scarthgap
and styhead.

    agherzan#1389

Signed-off-by: Bassem Nomany <[email protected]>
@BassemMohsen BassemMohsen changed the title mesa: update to 24.3.1 mesa: update to 24.3.1, wayland-protocol updated to 1.38 Dec 14, 2024
@BassemMohsen
Copy link
Author

@leon-anavi I'm still testing the build against meta-raspberrypi scarthgap latest.

Copy link
Contributor

@leon-anavi leon-anavi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent work! I have just tested again this patch against branch Scarthgap with the official 7" gen 1 touchscreen display and Raspberry Pi 5. Thanks to this patch Weston uses dri_gbm.so for both the microHDMI and the DSI.

@BassemMohsen
Copy link
Author

Amazing work @leon-anavi
Thanks a lot.

I did test with Qt Wayland on Poky Styhead and master meta-raspberrypi too.

In that case, I would say both PRs are ready for CI and merging unless anyone have more change requests.

# Remove unused patches
SRC_URI = "https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
file://0001-meson-misdetects-64bit-atomics-on-mips-clang.patch \
"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if it should be make rpi specific now by setting PACKAGE_ARCH to be MACHINE_ARCH

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, not sure I follow.
I don't see that variable in my bbappend. Can you show me example?

@@ -0,0 +1,30 @@
SUMMARY = "Collection of additional Wayland protocols"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this will override the core provided recipe and we may fail yocto project compatible checks. I wonder if there is a better solution for this.

Copy link
Author

@BassemMohsen BassemMohsen Dec 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, master branch is using 1.38 nowadays.
Not styhead though.
For the Pull request to master branch #1390 , I will remove it.

For Scarthgap, it can remain until scarthgap branch updaate wayland protocol.

I think the right answer is to update mesa and wayland protocol in Poky branches Scarthgap, Styhead and master.

But it's a tougher challenge since every board arch outhere uses poky, and they might want to freeze versions for scarthgap and styhead.
That means DSI will be broken for RPI5 scarthgap and styhead until and if poky accepts upgrading mesa and wayland protocool or never do it because they want to freeze versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants