| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
No idea why it's so hard to reproduce.
Broken with: c35572352e3e92683988ee8d151b47f4190d62f9
Thanks to Toni Spets for assistance.
|
| |
|
|
|
|
| |
Signed-off-by: Alex Deucher <[email protected]>
|
|
|
|
|
| |
Improves frame rate in apps with at least one user vertex buffer and
a hw index buffer.
|
| |
|
|
|
|
| |
Shouldn't happen, but you never know.
|
|
|
|
| |
We already have pb_buffer::reference::count.
|
| |
|
|
|
|
|
|
| |
v2: Allocate the fences from a single shared buffer object.
v3: Allocate the r600_fence structs in blocks of 16.
Spin a few times before calling sched_yield in r600_fence_finish().
|
|
|
|
|
|
| |
Fix build failures introduced with commit 0fbb64a52931ba5871aa2c5eb01b81d391f678d1.
Reviewed-by: Jakob Bornecrantz <[email protected]>
|
|
|
|
| |
Signed-off-by: Daniel Vetter <[email protected]>
|
|
|
|
| |
this is a port of the r300 winsys code to do the same thing.
|
|
|
|
|
|
| |
Spotted by Henri on IRC.
Signed-off-by: Alex Deucher <[email protected]>
|
|
|
|
|
|
|
|
| |
This packet is required when updating the DB, CB,
or STRMOUT base addresses on rv6xx for the surface
sync logic to work correctly.
Signed-off-by: Alex Deucher <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
The drivers have been changed so that they behave as if all of the flags
were set. This is already implicit in most hardware drivers and required
for multiple contexts.
Some state trackers were also abusing the PIPE_FLUSH_RENDER_CACHE flag
to decide whether flush_frontbuffer should be called.
New flag ST_FLUSH_FRONT has been added to st_api.h as a replacement.
|
|
|
|
|
|
|
| |
This fd gets passed in from outside, closing it causes the X.org server
to crap out when the driver doesn't identify the chipset.
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
| |
The build still fails.
|
|
|
|
| |
Thread offloading is not sometimes desirable, e.g. when mapping a buffer.
|
|
|
|
| |
Running any older kernel is not recommended anyway.
|
| |
|
|
|
|
|
|
|
| |
No one ever cared. libdrm does dynamic resizing of its reloc-table,
anyway.
Signed-off-by: Daniel Vetter <[email protected]>
|
|
|
|
|
|
|
|
| |
This is reliant on a drm patch that I posted on the list + a version bump.
These will appear in drm-next today.
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
If the drm minor version is > 9 (i.e. whats in drm-next),
we enable s3tc + texture tiling by default now.
this changes R600_FORCE_TILING to R600_TILING which can
be set to false to disable tiling on working drm.
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
|
| |
v2: Add the batch bo to the libdrm validation lost, for otherwise
libdrm won't take previously used buffers into account.
Signed-off-by: Daniel Vetter <[email protected]>
|
|
|
|
|
|
|
|
|
| |
These files can be decoded with intel_dump_decode from the intel-gpu-tools
available at:
http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/
Signed-off-by: Daniel Vetter <[email protected]>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
platform.system in SCons on Cygwin includes the OS version number.
Windows XP - CYGWIN_NT-5.1
Windows Vista - CYGWIN_NT-6.0
Windows 7 - CYGWIN_NT-6.1
Reduce all Cygwin platform variants to just 'cygwin' so anything
downstream can simply use 'cygwin' instead of the different full
platform names.
|
|
|
|
| |
Fixes immediate Python exceptions with SCons on Cygwin.
|
| |
|
|
|
|
|
|
| |
Intel classic drivers switched to this, too, so it must be good.
Signed-off-by: Daniel Vetter <[email protected]>
|
|
|
|
| |
Signed-off-by: Daniel Vetter <[email protected]>
|
| |
|
| |
|
|
|
|
|
|
| |
We're using bo_subdata.
Signed-off-by: Daniel Vetter <[email protected]>
|
| |
|
| |
|
|
|
|
| |
radeon_bo_unref may destroy the buffer, so call it after p_atomic_dec, not before.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is a multi-threading optimization which hides the kernel overhead
behind a thread. It improves performance in CPU-limited apps by 2-15%.
Of course you must have at least 2 cores for it to make any difference.
It can be disabled with:
export RADEON_THREAD=0
|
|
|
|
| |
Ooops.
|
|
|
|
|
| |
The VBO module uses both, but they are somewhat opposite to each other.
In this case, we pick UNSYNCHRONIZED and ignore DONTBLOCK.
|
|
|
|
| |
This is the last one I think.
|
|
|
|
|
|
|
|
|
|
| |
Because an app may do something like this:
while (!(ptr = bo_map(..., DONT_BLOCK))) {
/* Do some other work. */
}
And it would be looping endlessly if we didn't flush.
|
| |
|
|
|
|
| |
Accidentally negated in 685c3262b945a7f0e9f1f3a9409a12fdda08c828.
|
| |
|
|
|
|
|
| |
This should prevent calling into radeon_get_reloc when there's
only one context.
|
| |
|
| |
|