Displaying 2 results from an estimated 2 matches for "weston_log".
2014 May 30
0
[Bug 75761] weston-launch no output - black screen
...rtc, and then relies on that particular crtc to send back a pageflip
event as requested.
So if that's the culprit, is Nouveau on some particular hardware sending back
pageflip events on the wrong crtc? Or maybe mixing up crtcs so that no event
gets sent?
This would be easy to test by adding a weston_log("got pageflip event\n") to
src/compositor-drm.c:745, in function page_flip_handler(), and another in line
723 in vblank_handler(). The vblank_handler should be unused atm. I think.
If Weston never gets the pageflip event, its repaint loop would be stuck, which
would explain the symptoms....
2014 May 31
0
[Bug 75761] weston-launch no output - black screen
...However this is hard
for me to believe, as I think it would have caused problems with Xorg, too...
wouldn't it?
Or maybe Xorg is only looking at the vblank counters, and you'd actually need a
program using GLX_OML_sync_control to even see the timestamps?
One could check the timestamps by:
weston_log("%s: time %u.%06u frame %u\n", __func__, sec, usec, frame);
in compositor-drm.c page_flip_handler() function.
Mm, I'd like to see a weston log with that when you have the black screen
problem.
--
You are receiving this mail because:
You are the assignee for the bug.
--------------...