Conversation
- Sync with upstream: https://gitlab.freedesktop.org/mesa/mesa/-/commit/166c68914b494c45fbd9e4a736a0fe5867581b6a - Remove unofficial support for Adreno 830, as upstream has added official support: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/39874 - Remove unofficial support for Adreno 829, as upstream has added official support: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40655 - Remove patch "0019-UBWC_5-and-UBWC_6-support.patch", as upstream has merged it: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40758 - Update unofficial support for Adreno 810/825 from whitebelyash's patch: whitebelyash/mesa-tu8@e010ccc
|
@lfdevs Unfortunately, it seems it does not work on the The previous pull request build, which is now closed, works fine, but the latest pull request build does not work as shown below. Please check into this~ |
… is missing Note: This is a temporary fix patch, and upstream will fix this issue soon: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40823 After MR !37802, tu_autotune initialization treats missing CP perf counters as a fatal error and returns VK_ERROR_INITIALIZATION_FAILED. On newer A8xx devices where perf counter mappings may be incomplete, this breaks device creation and causes all Vulkan apps (including vulkaninfo) to fail. Make preempt latency tracking initialization degrade gracefully instead of failing device creation: - only probe CP counters when preempt tracking is supported - if CP group/countables/counters are missing, log a warning - disable PREEMPT_OPTIMIZE in both supported and active autotune config - continue initialization with VK_SUCCESS This keeps optional preempt optimization disabled on unsupported hardware while preserving normal Vulkan device creation.
|
I also encountered some issues when testing with Adreno 830 and reported them upstream: https://gitlab.freedesktop.org/mesa/mesa/-/work_items/15261 They should fix this problem in the future. The issue with Adreno 840 might be the same one. I also submitted a temporary fix patch, which might work: b1bce18 After the Actions build is complete, you can try it: https://github.com/lfdevs/termux-packages/actions/runs/24277350957?pr=9#artifacts |
|
@lfdevs I look forward to the new upstream after the issue is fixed! Thank you! |
Changelog
Installation and Usage Instructions
You can find the build artifacts here: https://github.com/lfdevs/termux-packages/actions/runs/24277350957?pr=9#artifacts
Specifically, look for files in the Artifacts section that start with
debs, such asdebs-aarch64-xxxxxx. After downloading and extracting it, you’ll obtainmesa_26.1.0_aarch64.debandmesa-vulkan-icd-freedreno_26.1.0_aarch64.deb.You can refer to the following commands to enable hardware acceleration using Turnip driver inside a Termux native container: