Sem-668: Re-enable EGLFS #21
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Vivante EGL/GLES into Qt sysroot and fail if eglfs_viv is missing
- enable -gbm/-kms during configure and drop the Vivante-specific packaging - extend the sysroot recipe with libdrm/libgbm/libegl Mesa headers/libs - require libegl1, libgbm1, libdrm2 at runtime and sanity-check eglfs_kms plugin
Qt.io is having constant issues with DDoS attacks so has become unreliable
There was a problem hiding this comment.
Pull request overview
This PR re-enables hardware-accelerated Qt rendering using EGLFS/KMS by configuring Qt with the necessary Mesa/GBM/DRM support, removing the previous Vivante-specific injection logic, and ensuring the required Mesa libraries and Qt plugins are packaged correctly for Bookworm.
Key Changes
- Qt build configuration now includes
-eglfs -gbm -kmsflags and removes software framebuffer overrides - Mesa/DRM development packages added to cross-compilation sysroot
- Vivante-specific header files and injection logic removed from the build process
Reviewed changes
Copilot reviewed 35 out of 62 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| tools/sysroot_multistrap.cfg | Adds Mesa/DRM development packages (libegl1-mesa-dev, libgles2-mesa-dev, libgbm-dev, libdrm-dev) to the cross-compilation sysroot |
| tools/vivante/imx8/include/HAL/* | Removes previously committed Vivante proprietary header files that are no longer needed with Mesa stack |
| tools/vivante/imx8/include/GLES3/* | Removes Vivante-specific GLES3 headers now replaced by standard Mesa headers |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
9 tasks
robinmdh
approved these changes
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR reintroduces a hardware‐accelerated Qt pipeline so Okuda can run on eglfs/KMS rather than the software framebuffer:
build.shnow configures Qt with-eglfs -gbm -kms(and removes the-linuxfb/-no-gbm/-no-kmsoverrides) so the EGLFS GBM plugin is built. The build now fails early if libqeglfs-kms-integration.so is missing after make install.tools/sysroot_multistrap.cfgpulls the Mesa/DRM dev packages (libegl1-mesa-dev, libgles2-mesa-dev, libgbm-dev, libdrm-dev) into the cross sysroot so the new plugin links.debian/control.indeclares the corresponding runtime deps (libegl1, libgbm1, libdrm2, libgles2) and the build verifies thatlibqeglfs-kms-integration.solands in/opt/qt/plugins/egldeviceintegrations.These changes produce a Qt package that ships the eglfs/KMS backend out of the box, along with the Mesa libraries it needs. Combined with the kernel work (etnaviv) and service updates, Okuda can run with vsync again on Bookworm.
The following are supplementary to this PR:
jedi-cookbook: : https://github.com/Ultimaker/jedi-cookbook/pull/294
um-kernel: Ultimaker/um-kernel#217
okuda: https://github.com/Ultimaker/okuda/pull/1207
How has this been tested
In combination with the packages from the PRs above: