- Aug 11, 2012
-
-
Marek Olšák authored
-
Marek Olšák authored
-
- Aug 10, 2012
-
-
Emma Anholt authored
Reviewed-by:
Ben Widawsky <ben@bwidawsk.net>
-
Emma Anholt authored
Reviewed-by:
Ben Widawsky <ben@bwidawsk.net>
-
Emma Anholt authored
It warns about totally sensible things done in intel_decode.c. I've never seen this warn do anything useful, and apparently I was the one to introduce it when I added the giant pile of warning flags back in 2008. Reviewed-by:
Ben Widawsky <ben@bwidawsk.net>
-
- Aug 09, 2012
-
-
Marek Olšák authored
Reviewed-by:
Jerome Glisse <jglisse@redhat.com>
-
Marek Olšák authored
Reviewed-by:
Jerome Glisse <jglisse@redhat.com>
-
Marek Olšák authored
If we don't need stencil, don't allocate it. If we need only stencil (like PIPE_FORMAT_S8_UINT), don't allocate depth. v2: actually do it correctly Reviewed-by:
Christian König <christian.koenig@amd.com>
-
Marek Olšák authored
Setting those flags has no effect anywhere else. Reviewed-by:
Christian König <christian.koenig@amd.com>
-
- Aug 08, 2012
-
-
Paulo Zanoni authored
Signed-off-by:
Paulo Zanoni <paulo.r.zanoni@intel.com> Reviewed-by:
Rodrigo Vivi <rodrigo.vivi@gmail.com>
-
Chris Wilson authored
Otherwise we end up with X hitting a fail-loop as the embedded libGL stacks asserts whilst initialising. Signed-off-by:
Chris Wilson <chris@chris-wilson.co.uk> Acked-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
- Aug 06, 2012
-
-
Alex Deucher authored
Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Alex Deucher authored
Noticed by: Harald van Dijk <fdo@gigawatt.nl> Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=53124 Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
- Aug 02, 2012
-
-
Emma Anholt authored
-
Signed-off-by:
Damien Lespiau <damien.lespiau@intel.com> Reviewed-by:
Eric Anholt <eric@anholt.net>
-
- Jul 23, 2012
-
-
Rob Clark authored
If color format for CRTC layer is not specified on commandline, then c->fourcc is unintialized resulting in addfb call failing. Signed-off-by:
Rob Clark <rob@ti.com>
-
- Jul 20, 2012
-
-
Laurent Pinchart authored
As the modeset test application is often referred to as an example of the KMS API usage, move test pattern generation and buffer allocation to a separate file to keep it simple and clear. Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
-
Laurent Pinchart authored
Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
-
Laurent Pinchart authored
This will make it easier to add additional parameters to the connector and plane arguments. Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
-
Laurent Pinchart authored
Implement tiles and SMPTE test pattern generation for the RGB565, BGR888, RGB888, ARGB8888, BGRA8888 and BGRX8888 formats. Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
-
Laurent Pinchart authored
Implement tiles and SMPTE test pattern generation for the NV12, NV21, NV16 and NV61 formats. Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
-
Laurent Pinchart authored
Implement tiles and SMPTE test pattern generation for the UYVY, VYUY and YVYU formats. Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
-
Laurent Pinchart authored
Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
-
Laurent Pinchart authored
Merge the create_test_buffer() and create_grey_buffer() functions into a single buffer allocation function that takes the pixel format and fill pattern as parameters. Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
-
Rob Clark authored
CCLD test_decode ./.libs/libdrm_intel.so: undefined reference to `drmPrimeHandleToFD' ./.libs/libdrm_intel.so: undefined reference to `drmPrimeFDToHandle' collect2: ld returned 1 exit status From Adam Jackson's explaination: most distros have changed it so ld defaults to --no-copy-dt-needed-entries, so if you use something from libdrm you can't just assume libdrm_intel will bring it in for you, you have to be explicit Signed-off-by:
Rob Clark <rob@ti.com>
-
- Jul 19, 2012
-
-
Dave Airlie authored
This adds interfaces for the X driver to use to create a prime handle from a buffer, and create a bo from a handle. v2: use Chris's suggested naming (well from at least for consistency) v3: git commit --amend fail v4: fix as per Chris's suggestions, group assignments, add get tiling Reviewed-by:
Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by:
Dave Airlie <airlied@redhat.com>
-
Dave Airlie authored
This adds prime support to nouveau libdrm. Signed-off-by:
Dave Airlie <airlied@redhat.com>
-
- Jul 16, 2012
-
-
Dave Airlie authored
These are just basic ioctl wrappers around the prime ioctls, along with the capability reporting. Reviewed-by:
Alex Deucher <alexander.deucher@amd.com> Signed-off-by:
Dave Airlie <airlied@redhat.com>
-
Dave Airlie authored
This just moves over some missing caps from the kernel. Signed-off-by:
Dave Airlie <airlied@redhat.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com>
-
- Jul 13, 2012
-
-
Rob Clark authored
There can be scenarios, especially when re-importing an existing buffer, where you end up with multiple 'struct omap_bo's wrapping a single GEM object handle. Which causes badness when the first of the evil-clones is omap_bo_del()'d. To do this, introduce reference counting and a hashtable to track the handles per fd. First, to avoid bo's slipping through the crack if multiple 'struct omap_device's are created for one drm fd, a hashtable mapping drm fd to omap_device, and the omap_device itself is reference counted. Per omap_device, we keep a handle_table mapping GEM handle to omap_bo. When buffers are imported from flink name or dmabuf fd, the handle table is consulted, and if an omap_bo already exists, it's refcnt is incremented and it is returned. For good measure, to avoid the handle_table being deleted before the omap_bo is freed, the omap_bo holds a reference to the omap_device. TODO: check the overhead of the hashtable. If too much we could maybe get away with only tracking exported and imported bo's in the table. TODO: all the import/export flink/dmabuf operations are generic DRM ioctls. Really all this functionality could be handled by a generic drm_bo and drm_device "base class" that could be extended by omap, exynos, etc. That would also allow more common userspace code by avoiding artificial libdrm_omap dependencies. Signed-off-by:
Rob Clark <rob@ti.com>
-
Rob Clark authored
Signed-off-by:
Rob Clark <rob@ti.com>
-
Rob Clark authored
Signed-off-by:
Rob Clark <rob@ti.com>
-
- Jul 12, 2012
-
-
Kenneth Graunke authored
Since there is no getparam for hardware context support, Mesa always tries to obtain a context by calling drm_intel_gem_context_create and NULL-checking the result. On an older kernel without context support, this caused libdrm to print an unwanted message to stderr: DRM_IOCTL_I915_GEM_CONTEXT_CREATE failed: Invalid argument In fact, this caused every Piglit test to fail with a "warn" status due to the unrecognized error message. Change the message to use DBG() rather than fprintf(), so people can still get the debug message, but it won't spam normally. Reviewed-by:
Ben Widawsky <ben@bwidawsk.net> Signed-off-by:
Kenneth Graunke <kenneth@whitecape.org>
-
- Jul 06, 2012
-
-
Cooper Yuan authored
-
- Jul 03, 2012
-
-
Hi list The recently released libdrm 2.4.37 does not compile the Intel part: test_decode.c: In function 'compare_batch': test_decode.c:107: error: implicit declaration of function 'open_memstream' PS: Please CC me. Signed-off-by:
Lauri Kasanen <cand@gmx.com> Signed-off-by:
Ben Widawsky <ben@bwidawsk.net>
-
- Jun 29, 2012
-
-
Ben Widawsky authored
Signed-off-by:
Ben Widawsky <ben@bwidawsk.net>
-
Ben Widawsky authored
Add relevant code to set up minimal state and call the appropriate kernel IOCTLs. This was missed in the previous cherry-picking for 2.3.36. Signed-off-by:
Ben Widawsky <ben@bwidawsk.net>
-
- Jun 28, 2012
-
-
Kristian Høgsberg authored
-
- Jun 27, 2012
-
-
Ben Widawsky authored
I mistakenly "fixed" a bad decode with commit 7d0a1d5e Author: Ben Widawsky <ben@bwidawsk.net> Date: Sun Jun 24 20:35:57 2012 -0700 intel/decode: VERTEX_ELEMENT_STATE, 1 means valid However the actual fix is just to update the reference file, and include GEN7 in the decode. Props to Eric Anholt for putting the test in distcheck, or else I wouldn't have caught this. Signed-off-by:
Ben Widawsky <ben@bwidawsk.net>
-
Ben Widawsky authored
This reverts commit 7d0a1d5e. The actual fix
-