| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
print the output target in the FP debug.
Signed-off-by: Dave Airlie <[email protected]>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
All these pointers are in the __DRIcontext struct, which we point to.
|
|
|
|
|
| |
With DRI2, x and y are always zero and fb->Height is always up to date
with the drawable height.
|
|
|
|
| |
Fixes progs/glsl/deriv.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
src/mesa/drivers/dri/intel/intel_mipmap_tree.c - left what was in master
|
| |
| |
| |
| |
| | |
Was broken since the endianness fixes.
(cherry picked from commit 4cf14fa80bda5f4ea65bef3a64e748e064d0bde1)
|
| |
| |
| |
| |
| | |
This probably broke the swrast DRI driver when running X in depth 16.
(cherry picked from commit 6ec259eb17dfbb74972b8cffb4e02a9dbab288cc)
|
| |
| |
| |
| |
| | |
Fixes piglit fbo-readdrawpix.
(cherry picked from commit 5782b2a968bb979b651e49bb5fc4162faa842050)
|
| |
| |
| |
| |
| | |
fixes piglit fbo-copypix.
(cherry picked from commit a589da14dee0c2a32e6e529f1a390b01a3ee4001)
|
| |
| |
| |
| |
| | |
Bug #26966: 945 miptree pitch disagreement with libdrm.
(cherry picked from commit da011faf48155a5c02ebc1fe1fa20a4f54b8c657)
|
| |
| |
| |
| | |
(cherry picked from commit 32f143b4327521a058dc05f0ab9087a5696b9618)
|
| |
| |
| |
| |
| |
| | |
If a non-zero src_y was used, this would break piglit
depth-level-clamp.
(cherry picked from commit e1e48ea15c1fe448f0b69e086b66c1123dc98bb7)
|
| | |
|
| |
| |
| |
| | |
I think my maths is right?
|
|\| |
|
| | |
|
| |
| |
| |
| | |
Spotted by Pauli Nieminen
|
| |
| |
| |
| |
| |
| |
| |
| | |
R300_PVS_MAX_CONST_ADDR field holds highest const addr, not
const count.
Fixes missing models and others rendering errors for vertex
program using 256 params.
|
| |
| |
| |
| | |
UMS will probably require some kernel work
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It may happen that the vertex attribute we were going to stuff
the wpos/fog attrs in was already written by vertex program.
In such cases we need to remove instruction accessing these
attributes, so they don't overwrite the wpos/fog related
instructions.
This fixes non-textured models in many wine games.
|
| |
| |
| |
| | |
removed FP during compilation
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We're still abusing the flags by putting them where our driver stores
ctx->NewState changes. Making them into more restricted state change
flags would be a project for later.
Fixes a failure where calling intel_draw_buffer() too often would trip
up Mesa assertions about when Mesa state could get changed, when it hadn't.
Bug #27034.
|
| |
| |
| |
| | |
Fixes #27213.
|
| | |
|
| |
| |
| |
| | |
meta ops should work ok without kms.
|
| |
| |
| |
| |
| | |
Fixes piglit glsl-orangebook-ch06-bump, regressed with
4fc57322258a750c0a9cabc77372b5ccde1fa877
|
| | |
|
| |
| |
| |
| |
| | |
_glapi_Context and _glapi_Dispatch have different constness between
TLS and non-TLS builds.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently the test link uses -lGL to define the glapi symbols.
This makes it impossible to build DRI drivers on systems without
Mesa installed and without building the libGL from the Mesa tree
first.
Some automated build systems trigger this problem.
This commit removes -lGL and instead adds a dummy implementation of
glapi to dri_test.c
This, along with Kristian's commit, should fix all known regressions
due to the addition of unresolved symbol checking.
|
| |
| |
| |
| | |
This will make sure we pick up libdrm_$(chipset).so from the right place.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We're still abusing the flags by putting them where our driver stores
ctx->NewState changes. Making them into more restricted state change
flags would be a project for later.
Fixes a failure where calling intel_draw_buffer() too often would trip
up Mesa assertions about when Mesa state could get changed, when it hadn't.
Bug #27034.
|
| |
| |
| |
| | |
Using just mv may cause prompts on some systems/configurations.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a different approach to solving this problem that the patch
I previously posted, and unlike that, should not cause any problems.
Right now undefined symbols in DRI drivers will still allow the
build to succeed.
As a result, people modifying drivers they cannot test risk creating
unloadable drivers with no easy way of automatically avoiding it.
For instance, the modifications to nv50 for context transfers caused
such an issue recently.
Unfortunately, just adding -Wl,--no-undefined doesn't work, because
the DRI drivers depend on glapi symbols, but do not depend on
libGL.so.1
Adding -lGL is not the correct solution since DRI drivers are not loaded
just by libGL, but also by X and possibly by other clients.
So, this patch simply tries to build an executable linked to the DRI
driver and to libGL.
If the DRI driver contains any undefined symbols not satisfied by its
dependencies or by libGL, this will fail.
This solution does not alter the built drivers, and does not significantly
slow down the build process.
All classic DRI drivers as well as all the Gallium drivers with configure
options compiled successfully with this change.
Thanks to Xavier Chantry <[email protected]> and
Michel Daenzer <[email protected]> for helping with this.
Signed-off-by: Luca Barbieri <[email protected]>
Acked-by: Brian Paul <[email protected]>
|
| | |
|
| |
| |
| |
| | |
Rejecting all doesn't seem to be helping get the pipeline lit up.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
It appears that the thing that was killing VS threads was the
gratuitous NOP that replaced the gratuitous jump from OPCODE_END to
the nearby OPCODE_END implementation. With that gone, we can move on
to the rest of the pipeline.
|
| |
| |
| |
| |
| |
| | |
Just emit the URB write at END time. Subroutine code that sits after
OPCODE_END won't be executed since we've ended the thread at the point
that the URB write is done.
|
| |
| |
| |
| |
| | |
Otherwise, we may not get the FFTID set up which would break freeing
of resources.
|
| |
| |
| |
| |
| |
| |
| | |
The hope is to later take advantage of the reduced constant usage to
free up regs. This only covers the GLSL path at the moment, because
the brw_wm_emit path doesn't get the information as to whether a float
value is a constant or a uniform.
|
| |
| |
| |
| |
| | |
I keep finding the desire to force this path to debug it instead of
cooking up goofy-looking testcases to do so.
|