- Dec 23, 2010
-
-
Julien Cristau authored
-
- Dec 14, 2010
-
-
Sven Joachim authored
The latter is deprecated, and we're build-depending on a new enough debhelper to use the former.
-
Sven Joachim authored
Mostly for documentary purposes, the numbers do not really matter.
-
Sven Joachim authored
Upstream broke the ABI of libdrm-nouveau without changing soname, so we have to change at least the package name. Install a new lintian override for the package-name-doesnt-match-sonames warning.
-
Sven Joachim authored
-
Sven Joachim authored
-
- Dec 10, 2010
-
-
Chris Wilson authored
To export new kernel API for Intel's 2010Q4 release. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
Chris Wilson authored
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
- Dec 07, 2010
-
-
Chris Wilson authored
gen4+ hardware doesn't use fences for GPU access and the older kernel doesn't expect userspace to make such a mistake. So don't. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=32190 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
Dave Airlie authored
this can remove nodes it shouldn't, let udev run the show. this is needed for reliably GPU switch. Signed-off-by: Dave Airlie <airlied@redhat.com>
-
- Dec 03, 2010
-
-
Chris Wilson authored
... but only account for a fenced used if the object is tiled. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
- Dec 02, 2010
-
-
Marek Olšák authored
-
- Nov 25, 2010
-
-
Chris Wilson authored
... so that intel_bufmgr.h can be compiled standalone. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
- Nov 22, 2010
-
-
Chris Wilson authored
For relaxed fencing the object may only consume the small set of active pages, but still requires a fence region once bound into the aperture. This is the size we need to use when computing the maximum possible aperture space that could be used by a single batchbuffer and so avoid hitting ENOSPC. Reported-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
Francisco Jerez authored
It makes sure that GPU object destruction is executed in order with respect to the previous FIFO commands. Signed-off-by: Francisco Jerez <currojerez@riseup.net> Acked-by: Ben Skeggs <bskeggs@redhat.com>
-
- Nov 09, 2010
-
-
Eric Anholt authored
Both the consumers of this API (sync objects and client throttling) were expecting this behavior. The kernel used to actually behave the desired (but incorrect) way for us anyway, but that got fixed a while back.
-
- Nov 07, 2010
-
-
Cyril Brulebois authored
-
Cyril Brulebois authored
-
Albert Damen authored
If bufmgr.bo_mrb_exec is not set, drm_intel_bo_mrb_exec returns ENODEV even though drm_intel_gem_bo_mrb_exec2 will work fine for the RENDER ring. Fixes xf86-video-intel after commit 'add BLT ring support' (5bed685f76) with kernels without BSD or BLT ring support (2.6.34 and before). Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=31443 Signed-off-by: Albert Damen <albrt@gmx.net> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> (cherry picked from commit 49447a9b) Signed-off-by: Cyril Brulebois <kibi@debian.org>
-
Albert Damen authored
If bufmgr.bo_mrb_exec is not set, drm_intel_bo_mrb_exec returns ENODEV even though drm_intel_gem_bo_mrb_exec2 will work fine for the RENDER ring. Fixes xf86-video-intel after commit 'add BLT ring support' (5bed685f76) with kernels without BSD or BLT ring support (2.6.34 and before). Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=31443 Signed-off-by: Albert Damen <albrt@gmx.net> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
Chris Wilson authored
The kernel has always allowed userspace to underallocate objects supplied for fencing. However, the kernel only allocated the object size for the fence in the GTT and so caused tiling corruption. More recently the kernel does allocate the full fence region in the GTT for an under-sized object and so advertises that clients may finally make use of this feature. The biggest benefit is for texture-heavy GL games on i945 such as World of Padman which go from needing over 1GiB of RAM to play to fitting in the GTT! Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> (cherry picked from commit 36245771) Signed-off-by: Cyril Brulebois <kibi@debian.org>
-
Chris Wilson authored
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> (cherry picked from commit 057fab33) Signed-off-by: Cyril Brulebois <kibi@debian.org>
-
- Nov 02, 2010
-
-
Eric Anholt authored
The intent of these was to catch mismatched map/unmap. What it actually did was check whether there was ever a mapping of that type (including in a previous life of the buffer through the userland BO cache), not whether they were mismatched. We don't even actually want to catch mismatched map/unmap, unless we also do refcounting, since at one point Mesa would do map/map/use/unmap/unmap. Just remove this code instead.
-
Eric Anholt authored
This couldn't be triggered except by overflow, since there's an assert in unreference to catch the usual failure of over-unreferencing.
-
- Nov 01, 2010
-
-
Eric Anholt authored
-
Eric Anholt authored
-
- Oct 31, 2010
-
-
Francisco Jerez authored
nouveau_bo_unmap called the CPU_FINI IOCTL even if it was a NOSYNC mapping. It caused no harmful effects (actually CPU_FINI is a no-op on recent enough kernels) besides the precious CPU cycles being wasted. Signed-off-by: Francisco Jerez <currojerez@riseup.net>
-
- Oct 29, 2010
-
-
Chris Wilson authored
The kernel has always allowed userspace to underallocate objects supplied for fencing. However, the kernel only allocated the object size for the fence in the GTT and so caused tiling corruption. More recently the kernel does allocate the full fence region in the GTT for an under-sized object and so advertises that clients may finally make use of this feature. The biggest benefit is for texture-heavy GL games on i945 such as World of Padman which go from needing over 1GiB of RAM to play to fitting in the GTT! Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
- Oct 27, 2010
-
-
Adam Jackson authored
_DRM_MALLOC hasn't been a relevant concern since we split libdrm out from xserver. Signed-off-by: Adam Jackson <ajax@redhat.com>
-
- Oct 26, 2010
-
-
Chris Wilson authored
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
- Oct 21, 2010
-
-
Francisco Jerez authored
Signed-off-by: Francisco Jerez <currojerez@riseup.net>
-
- Oct 12, 2010
-
-
Francisco Jerez authored
Signed-off-by: Francisco Jerez <currojerez@riseup.net> Acked-by: Ben Skeggs <bskeggs@redhat.com>
-
Francisco Jerez authored
Signed-off-by: Francisco Jerez <currojerez@riseup.net> Acked-by: Ben Skeggs <bskeggs@redhat.com>
-
- Oct 01, 2010
-
-
Cyril Brulebois authored
-
Chris Wilson authored
As the higher layers check the error return from libdrm-intel and are supposed to handle the error (and print their own warning in extremis) the voluminous output on stderr is just noise and a hazard in its own right. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
- Sep 29, 2010
-
-
Sven Joachim authored
-
Sven Joachim authored
-
Carl Worth authored
For the upcoming 2.4.22 release.
-
- Sep 25, 2010
-
-
Chris Wilson authored
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-
- Sep 21, 2010
-
-
Ben Skeggs authored
... and make a mental note to not push commits before having coffee Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
-