Implement remote framebuffer for GBM backend
76f0377a6145
Actions

Authored by Kanedias on Apr 30 2016, 11:01 PM.

Description

Implement remote framebuffer for GBM backend

This commit introduces a way to pass drawn buffers to remote side for
GBM backend. The buffers are not released till the notification comes
from the remote side they are no longer needed. It is possible to
achieve since the default Mesa GBM implementation gives 4 surfaces to
any created gbm_surface.

This feature is turned off by default, the environment variable
KWIN_REMOTE=1 enables this behaviour. The fds of GBM buffers are
passed by the means of wayland server and custom protocol.

Details

Committed

Kanedias

Oct 24 2017, 6:30 AM

Parents

R108:2a13a292eacb: [platforms/fbdev] Support for RGBA8888 color format

Branches

Unknown

Tags

Unknown

Kanedias committed R108:76f0377a6145: Implement remote framebuffer for GBM backend (authored by Kanedias).Oct 24 2017, 6:30 AM

Changes (9)

				Path	Packages
	M			main_wayland.cpp
	M			plugins/platforms/drm/CMakeLists.txt
	M			plugins/platforms/drm/drm_backend.cpp
	M			plugins/platforms/drm/drm_buffer_gbm.h
	M			plugins/platforms/drm/drm_output.h
	M			plugins/platforms/drm/egl_gbm_backend.cpp
	M			plugins/platforms/drm/egl_gbm_backend.h
	A			plugins/platforms/drm/remoteaccess_manager.cpp
	P			plugins/platforms/drm/remoteaccess_manager.h Copied from plugins/platforms/drm/gbm_surface.h