[Mesa-dev] [PATCH 2/2] gbm: Use libkms to work around missing cursor support in dri drivers

[Scott Moreau]

*snip*

>> Reviewed-by: Kristian Høgsberg <krh at bitplanet.net>
> >
> >
> > I briefly tested these patches on RV350 and it fixes the problem here
> > https://bugs.freedesktop.org/show_bug.cgi?id=52267
> > I did notice that the last frame of the last instance of weston is
> 'flashed'
> > during the fade-in when running the next instance of weston.
>
> Since Jakob added gbm_bo_write support now, I think you're now (for
> the first time) using hw cursor instead of gl cursor.  The flicker
> could be the RV350 flickering when we enable the hw cursor after the
> fade finishes.  You can try adding return NULL; early in
> drm_output_prepare_cursor_surface() to disable hw cursor and see if
> that's the case.
>
> Kristian
>

This does not seem to be the case. When weston starts, the last frame from
the last instance of weston is shown, then during fade-in, it is all black.
Specifically, it's black for about a half second and then weston appears
when the fade-in is nearly complete and you can tell damage from the fade
animation is still happening because the cursor is slower. Subsequent fades
work fine. If switched to X and back to tty, it then shows garbage from the
pixels of whatever X was showing.

Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20120820/3d9d976f/attachment-0001.html>