Of all the things I've tried, this seems to be the only thing
to fix tile corruptions reliably on gen2&gen3 (safe for outright
disabling the render copy).
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
That little snippet creapt in and magically made render copy work -
by essentially disabling it.
Restore order, everything incoherent again.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
It seems to be randomly broken, every boot in a slightly different
way on my i945gme. Works quite well on my Q35. So add an option to
disable it till this is resolved.
Well, more testing seems to suggest that I've been hunting ghosts.
Or maybe not and it works now simply because it's a different day.
Anyway, leave this in for future testing.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
gem_stress maps all buffers, so more only results in trashing (which
should be handled with an option).
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
ddx and mesa assume that this is issued after every blit command.
Breaking that invariant results in a dying gpu.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Some versions of libpciaccess on Linux set rom_size to 0 for VGA
devices. While this behavior may change, intel_bios_dumper should
handle this situation to be compatible with current versions of the
library.
This fixes segmentation faults on affected systems.
Signed-off-by: Forest Bond <forest.bond@rapidrollout.com>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
The busy bo has a fixed size (1024x256, 32bpp) whereas the scratch bo
may need to vary their size to exercise different features of fence
allocation.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
And a few other things:
- inline checking when copying tiles with the cpu, fails _much_ faster.
- bo size seems to have a tremendous effect, put on the TODO.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Move the loop operations around for test_all_modes so that it is clearly
split up into the desired phases.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
We have not a unified tool to check Intel display driver and we plan to use
intel-gpu-tools/testdisplay to check Intel display driver even though some
function tests can be found in libdrm/test. 3 new features are added:test
all supported modes, force mode and dump mode info(dump mode info is based on
libdrm/tests/modetest).
[ickle: attack the whitespacing!]
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
intel_bios_reader.c: In function ‘dump_backlight_info’:
intel_bios_reader.c:192:22: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘unsigned int’ [-Wformat]
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
intel_disable_clock_gating.c: In function ‘main’:
intel_disable_clock_gating.c:38:11: warning: unused variable ‘temp’ [-Wunused-variable]
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
It has been supersede by intel_error_decode for the user-facing role of
obtaining debug info after a crash.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>