Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This should go away before we push the code.
|
|
|
|
|
|
|
|
even with vs disabled, still doesn't work.
|
|
Now things catch on fire.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It hangs the GPU at the clipper stage, presumably because we're lacking
other setup.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(cherry picked from commit 293f4d51b473783d5c5ab773a1c438e0a2fe46f2)
|
|
|
|
|
|
PRE_EMIT_STATE_BUFSZ accounts for the start 3d, idle, cd/db flush
not for state. The relocs for CB_COLOR0_FRAG & CB_COLOR0_TILE
are part of the render target state.
|
|
this moves the emission outside the lock and adds r200 support.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
The kernel lets you clear depth without getting a depth offset
from userspace, mesa used to emit state before clear, but that got
lost in the refactoring, which made the kernel bug show up. Fix
mesa driver to emit the state properly now.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
This restores old behaviour, where we end up doing a DRI2GetBuffers()
call from intelMakeCurrent(). The idea was that we could do this
lazily, just before we start rendering. However, if we don't do the
DRI2GetBuffers() round-trip we don't get the drawable size and higher
level mesa ends up short-cutting a number of GL calls, such as glClear().
|
|
Tested with piglit glsl-arb-fragment-coord-conventions.
|