| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise simple apps like glxgears pick up a DirectColor visual since the X
server mixes the depth 32 visual in with the other GLX visuals, and this seems
to result in a (mostly) black screen due to a bad ColorMap for a lot of people.
The bad ColorMap may be a bug in the apps, the X server or X driver, and
regardless of that I think the X server should ideally make the depth 32 GLX
visual separate from the rest again, but in the meantime this makes us cope.
(depth_bits is either 16 or 24, never 0)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | | |
into r6xx-rewrite
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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 <[email protected]>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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 <[email protected]>
|
| | | |
|
| | |
| | |
| | |
| | | |
patch from Kevin DeKorte with some minor fixes from me.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | | |
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
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Move all the metaops to a dri_metaops file and port radeon/intel
to use the new common meta ops code.
|
| | |
| | |
| | |
| | |
| | | |
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.
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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 <[email protected]>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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 <[email protected]>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Split initializations becase the vars are of different type.
Reported-by: Nicolai Hähnle <[email protected]>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Reported-by: Nicolai Hähnle <[email protected]>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Reported-by: Nicolai Hähnle <[email protected]>
|
| | | |
| | | |
| | | |
| | | | |
Reported-by: Nicolai Hähnle <[email protected]>
|
| | | |
| | | |
| | | |
| | | | |
Reported-by: Nicolai Haehnle <[email protected]>
|
| | | | |
|