On Thu, 22 Sep 2011 16:27:11 -0700, Ben Widawsky b...@bwidawsk.net wrote:
+/**
+ * unmap an object in the non-blocking mode
+ */
+int drm_intel_gem_bo_unmap_nonblocking(drm_intel_bo *bo)
+{
+ drm_intel_bufmgr_gem *bufmgr_gem = (drm_intel_bufmgr_gem *) bo-bufmgr;
+ int ret = 0;
+
+
On Thu, Oct 06, 2011 at 01:55:49PM -0700, Eric Anholt wrote:
On Thu, 22 Sep 2011 16:27:11 -0700, Ben Widawsky b...@bwidawsk.net wrote:
+/**
+ * unmap an object in the non-blocking mode
+ */
+int drm_intel_gem_bo_unmap_nonblocking(drm_intel_bo *bo)
+{
+ drm_intel_bufmgr_gem
From: Daniel Vetter daniel.vet...@ffwll.ch
This adds a new mode to map gem objects in a non-blocking way.
The new kernel interface required to get the caching level/coherency
is not yet wired up. All the code to transparently choose between gtt
mappings or (if coherent) cpu mappings is already
On Thu, Sep 22, 2011 at 04:35:20PM -0700, Ben Widawsky wrote:
From: Daniel Vetter daniel.vet...@ffwll.ch
This adds a new mode to map gem objects in a non-blocking way.
The new kernel interface required to get the caching level/coherency
is not yet wired up. All the code to transparently
From: Daniel Vetter daniel.vet...@ffwll.ch
This adds a new mode to map gem objects in a non-blocking way.
The new kernel interface required to get the caching level/coherency
is not yet wired up. All the code to transparently choose between gtt
mappings or (if coherent) cpu mappings is already
This adds a new mode to map gem objects in a non-blocking way. This
needs to be enabled on a per-object basis with object_enable_nonblocking.
The new kernel interface required to get the caching level/coherency
is not yet wired up. All the code to transparently choose between gtt
mappings or (if
On Wed, 21 Sep 2011 10:19:13 +0200, Daniel Vetter daniel.vet...@ffwll.ch
wrote:
This adds a new mode to map gem objects in a non-blocking way. This
needs to be enabled on a per-object basis with object_enable_nonblocking.
The new kernel interface required to get the caching level/coherency
This adds a new mode to map gem objects in a non-blocking way.
The new kernel interface required to get the caching level/coherency
is not yet wired up. All the code to transparently choose between gtt
mappings or (if coherent) cpu mappings is already in place, though.
To make this useable for