<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - regression bisected black screen with cursor" href="https://bugs.freedesktop.org/show_bug.cgi?id=110030#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - regression bisected black screen with cursor" href="https://bugs.freedesktop.org/show_bug.cgi?id=110030">bug 110030</a> from <a class="email" href="mailto:2kmm@gmx.de" title="Manuel Mommertz <2kmm@gmx.de>"> Manuel Mommertz</a> <pre>(In reply to Maarten Lankhorst from <a href="show_bug.cgi?id=110030#c5">comment #5</a>) > 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. :/</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>