| Age | Commit message (Collapse) | Author |
|---|
|
1: add rv530 support
- num z pipes cap
- add proper start/finish query options for rv530
2: convert to use linked list properly.
3: add flushing required check.
4: initial Z top disabling support.
TODO:
make it actually work on my rv530.
|
|
This attempts to make r300g do proper bo space checking as opposed
to whatever it was doing now.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
to reproduce, start texrect, disable 0 texture in menu.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
It gets really annoying watching r300g tell me how it's filling surfaces.
Or falling back during filling surfaces.
|
|
Still not sure why st keeps handing down things we can't render to.
|
|
|
|
|
|
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
this makes the default state same as r300
|
|
|
|
Conflicts:
src/gallium/drivers/r300/r300_tgsi_to_rc.c
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
So I didn't touch r300compiler, but r300g now compiles after having
declarations and code untangled. As nha so gently points out, we shouldn't
have to do this just to comply with MSVC compilers.
|
|
We now have 48 GLX visuals. Pretty soon, we'll have 90+ visuals,
only five of which ever get tested. :3
|
|
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
Note that control flow instruction support isn't actually fully functional yet.
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
|
|
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
This fixes the glxgears bug, among other things.
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
Always test for PIPE_TRANSFER_READ/WRITE using the bit-wise and operator, and
add a pipe_transfer_buffer_flags() helper for getting the buffer usage flags
corresponding to them.
|
|
why there are two input position semantic tags is that ureg doesn't
set vs input semantic due to commit: 6d8dbd3d1ec888
so use vs input index instead of semantic name.
|
|
|
|
It could be generated by vertex shader.
|
|
Not sure why we are getting a shader with two inputs with position semantic, but we don't know how to handle it correctly so it's better to stop the app than lock the machine.
|
|
|
|
|
|
|
|
Not 100% sure this is correct, but its more correct than what was here previous
however it may require changes in the input routing for the frag shader.
|
|
|
|
also enable cube/3d bits in txformat reg
|
|
No point passing things twice here, also allows more state
to be setup properly.
|
|
|
|
Its not like it works well on 1.3 so may as well reach for greater
heights.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
pitch is pixels - 1, not bytes.
|
|
|
|
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
There were additional non-textual conflicts.
Conflicts:
src/gallium/drivers/r300/r300_tgsi_to_rc.c
src/mesa/drivers/dri/r300/compiler/r3xx_vertprog.c
src/mesa/drivers/dri/r300/compiler/radeon_program.c
src/mesa/drivers/dri/r300/compiler/radeon_program_alu.c
|
|
No longer used. S3TC support is queried via
pipe_screen::is_format_supported.
|
|
|
|
Individual texture images have a stride, but textures as a whole do not.
There are still pieces of code which are confused about this, but the core of
the confusion is hopefully gone.
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
it can fix redbook/sceneflat, scene, scenebamb, surface, nurbs and so on
|
|
Seriously guys....
|
|
So that debugging is no longer a full-spam-or-nothing approach, you are now
supposed to set the RADEON_DEBUG environment flag just like for classic Mesa.
The available debug flags are different, however. Just running an OpenGL
application with RADEON_DEBUG set to an arbitrary string will print out
helpful information.
Everything must be compiled with -DDEBUG for any of this to work
|
|
Conflicts:
src/gallium/drivers/r300/r300_tgsi_to_rc.c
|
|
according to actual vertex index count.
|
|
|
|
|
|
|
