• Daniel Stone's avatar
    compositor-drm: Add explicit type member to drm_fb · fc175a7e
    Daniel Stone authored
    Rather than magically trying to infer what the buffer is and what we
    should do with it when we go to destroy it, add an explicit type
    instead.
    
    In doing so, the test for dumb images (destroying them, but only if
    they're not the 'live' ones) is removed. This was dead code, as the only
    path which could cause us to shuffle images is drm_output_switch_mode.
    This calls drm_output_release_fb before the images are reallocated in
    drm_output_fini_pixman / drm_output_init_pixman, with the reallocation
    unconditionally destroying the images, so can never be hit.
    Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
    Reviewed-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
    fc175a7e
Name
Last commit
Last update
clients Loading commit data...
compositor Loading commit data...
data Loading commit data...
desktop-shell Loading commit data...
doc/doxygen Loading commit data...
fullscreen-shell Loading commit data...
ivi-shell Loading commit data...
libweston Loading commit data...
libweston-desktop Loading commit data...
m4 Loading commit data...
man Loading commit data...
protocol Loading commit data...
shared Loading commit data...
tests Loading commit data...
tools/zunitc Loading commit data...
wcap Loading commit data...
xwayland Loading commit data...
.gitignore Loading commit data...
COPYING Loading commit data...
Makefile.am Loading commit data...
README Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
notes.txt Loading commit data...
releasing.txt Loading commit data...
weston.ini.in Loading commit data...