| Age | Commit message (Collapse) | Author |
|---|
|
into r6xx-rewrite
|
|
patch from Kevin DeKorte with some minor fixes from me.
|
|
A context or surface that is neither linked to a display nor current to
a thread should be destroyed. Therefore, an unlinked context or surface
implies a pending delete automatically.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
This commit uses the newly introduced link functions to manage EGL
contexts and surfaces. As a result of this, the API for drivers are
changed. All drivers are updated for the change.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
|
|
|
|
|
|
You always need to emit a fetch shader (fs) even if you
aren't using it. For now, just emit the fs with the
vs address to make the kernel happy.
|
|
|
|
Spotted by kdekorte on IRC
|
|
|
|
|
|
|
|
Somehow context->radeon.tcl.aos[j].bo is not null sometimes,
but it is safe for now because it is only a pointer to
dma.current so overwriting it would not hurt anything.
|
|
|
|
|
|
|
|
into r6xx-rewrite
This builds, but I get an assertion in radeonGetLock() due to
the drawable being null.
|
|
|
|
This alleviates the need for an additional symbol.
|
|
tested on r500 with zreaddraw with Z buffer in all 3 modes
|
|
|
|
this uses the correct formula for macro tiled buffers for readback
|
|
since the surfaces aren't linear you can't just use GET_PTR
|
|
|
|
This allows double buffered apps to run, but perfomance
will be awful until we implement something faster.
You must update to the latest kernel modules.
|
|
Move all the metaops to a dri_metaops file and port radeon/intel
to use the new common meta ops code.
|
|
We were using sparse indexing for aos, while the common
code expected packed indexing.
|
|
|
|
This function takes a GLint not a GLuint, passing in -1
breaks internally.
|
|
Fixes new piglit depthrange-clear.c test.
|
|
RasterPos[2] is already sent through the window transform, which includes
DepthRange handling. So make DepthRange for the metaops a noop.
Fixes a failure in oglconform depthrange.c
|
|
This is just following bind_vertex_array()'s behavior.
|
|
|
|
Fixes those formats in fbo_firecube.
Only tested with r300, radeon and r200 compile tested only.
|
|
Fixes fgl_glxgears and progs/demos/fbotexture after pressing 'c'.
Tested with r300, radeon and r200 compile tested only.
|
|
|
|
|
|
Really, we should be checking that the MesaTexFormat for the read buffer
and the texture match, but the previous code wasn't even doing that, so
matching the cpp should be an improvement (and potentially fix some hangs!).
The previous code also rejected GL_RGB even though blitting the alpha
channel to the ignored channel of an x8r8g8b8 texture should be fine, which
tripped up compiz's blur plugin.
|
|
Components of input attributes that are used by fragment program aren't part of vertex program key, and that may lead to situations when vertex program writes only TEX1.xy and fragment program reads TEX1.xyz, resulting in rendering errors.
Reported-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
We only care about the actual fogcoord itself now, reducing the rewriting
done for the vertex program.
The rewriting of source operand swizzles in the fragment program takes
care that fogcoord.yzw = 001.
This should fix fogcoord rewriting entirely, which had been horribly
broken in the face of dot-product instructions, and just broken (though
not horribly so) in the face of almost every other instruction (the W
component would be incorrect for most arithmetic instructions).
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
|
|
Split initializations becase the vars are of different type.
Reported-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
|
|
Reported-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
|
|
Reported-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
Reported-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
Reported-by: Nicolai Haehnle <nhaehnle@gmail.com>
|
|
|
