diff options
| author | Laszlo Agocs <laszlo.agocs@qt.io> | 2022-09-19 12:58:05 +0200 |
|---|---|---|
| committer | Laszlo Agocs <laszlo.agocs@qt.io> | 2022-09-22 17:31:31 +0200 |
| commit | 820775166132b073a941f2389fba81db49619688 (patch) | |
| tree | 4e38f7f8c3b9d57d50b2305e18501b8e0df2d51d /tests/auto/gui/rhi/qshader/tst_qshader.cpp | |
| parent | 95a3f85a2fae7dc44c1351475e00b93c9b527a7e (diff) | |
eglfs: Add env.var. to disable the dedicated drmHandleEvent thread
Setting QT_QPA_EGLFS_KMS_NO_EVENT_READER_THREAD=1 makes it operate
like it did before 5.12.7: just calling drmhandleEvent (guarded by
a mutex) on the current (main or render, depending on the QQ render
loop) thread.
This should not be needed and is discouraged (will certainly cause
deadlocks in multiscreen setups + QQ threaded render loop on certain
embedded systems), but it seems necessary to provide a way to revert
back to the old way of functioning as there are reports about
problems with screen cloning when the dedicated event reading thread
is used.
Task-number: QTBUG-91882
Pick-to: 6.4 6.3 6.2 5.15
Change-Id: I4cddcd09149dcab9e135467b6ef0e047a2a0ecff
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Andy Nichols <andy.nichols@qt.io>
Diffstat (limited to 'tests/auto/gui/rhi/qshader/tst_qshader.cpp')
0 files changed, 0 insertions, 0 deletions