[Bug 110030] regression bisected black screen with cursor

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Mar 15 11:57:16 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=110030

--- Comment #6 from Manuel Mommertz <2kmm at gmx.de> ---
(In reply to Maarten Lankhorst from comment #5)
> The pointers are just locations in memory, any difference in timing can
> cause them to change. :)

I know what pointers are. ;) The point is that the call to 'drm_pick_crtcs'
switched the associated crtcs between the outputs (look at the test-patch, the
addresses are from the same run; once before, once after call to the function).
And with this call added, X starts as expected.

drm_pick_crtcs looks hard to find the best match between connector and crtc
while intel_fb_initial_config just uses the first crtc that has a matching
mode.

So without understanding what all this stuff is, I come to the conclusion that
the right association between connector and crtc is essential.
If the kernel now does not try its best to find this right association, the
modesetting driver has to do it. I have looked at the code, tried some changes
but with no success. It is just to complex for me to understand enough to fix
this myself. :/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190315/dde24ab4/attachment.html>


More information about the intel-gfx-bugs mailing list