summaryrefslogtreecommitdiff
path: root/src/cairo-debug.c
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2009-06-11 15:18:55 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2009-07-23 16:18:42 +0100
commitc3f2db4f73e93a3dafe0f52a5f9ca09ca78cc906 (patch)
tree5cb530cb949e950370c2ff4866c560b1a1075b6f /src/cairo-debug.c
parentbed2701e1c89095878d549cbca8f22d84f3dda3c (diff)
[drm] Add an accelerated image surface.
Use the DRM interface to h/w accelerate composition on image surfaces. The purpose of the backend is simply to explore what such a hardware interface might look like and what benefits we might expect. The use case that might justify writing such custom backends are embedded devices running a drm compositor like wayland - which would, for example, allow one to write applications that seamlessly integrated accelerated, dynamic, high quality 2D graphics using Cairo with advanced interaction (e.g. smooth animations in the UI) driven by a clutter framework... In this first step we introduce the fundamental wrapping of GEM for intel and radeon chipsets, and, for comparison, gallium. No acceleration, all we do is use buffer objects (that is use the kernel memory manager) to allocate images and simply use the fallback mechanism. This provides a suitable base to start writing chip specific drivers.
Diffstat (limited to 'src/cairo-debug.c')
-rw-r--r--src/cairo-debug.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/src/cairo-debug.c b/src/cairo-debug.c
index 4dccebeb..4409e6eb 100644
--- a/src/cairo-debug.c
+++ b/src/cairo-debug.c
@@ -77,6 +77,10 @@ cairo_debug_reset_static_data (void)
_cairo_clip_reset_static_data ();
+#if CAIRO_HAS_DRM_SURFACE
+ _cairo_drm_device_reset_static_data ();
+#endif
+
CAIRO_MUTEX_FINALIZE ();
}