Skip to content
Snippets Groups Projects
Commit a46a8097 authored by Pekka Paalanen's avatar Pekka Paalanen
Browse files

compositor-fbdev: always destroy renderer-output on disable


If we pass the base->enabled test, then the renderer output is
guaranteed to be there, so we can just destroy it.

Destroying it before unmap makes the sequence match better the enable
path.

Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
parent 08e41b58
No related branches found
No related tags found
No related merge requests found
...@@ -486,11 +486,9 @@ fbdev_output_disable_handler(struct weston_output *base) ...@@ -486,11 +486,9 @@ fbdev_output_disable_handler(struct weston_output *base)
if (!base->enabled) if (!base->enabled)
return 0; return 0;
pixman_renderer_output_destroy(&output->base);
fbdev_frame_buffer_unmap(output); fbdev_frame_buffer_unmap(output);
if (base->renderer_state != NULL)
pixman_renderer_output_destroy(base);
return 0; return 0;
} }
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment