compositor-fbdev: always destroy renderer-output on disable
authorPekka Paalanen <pekka.paalanen@collabora.co.uk>
Wed, 13 Sep 2017 14:22:38 +0000 (17:22 +0300)
committerPekka Paalanen <pekka.paalanen@collabora.co.uk>
Wed, 4 Oct 2017 13:18:06 +0000 (16:18 +0300)
commit61e5a2727a0625a7f082ced749b6d41f88ea84e3
tree152e955f60def98ca50eb76206e84a6123d5af13
parenta51e71fbf0b3b1faceca2fb1272728177c56951d
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 <pekka.paalanen@collabora.co.uk>
Reviewed-by: Ian Ray <ian.ray@ge.com>
Acked-by Daniel Stone <daniels@collabora.com>
libweston/compositor-fbdev.c