| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Initial version contributed by: Martin Andersson <[email protected]>
This is only used if the memcpy path cannot be used and if no transfer ops
are needed. It's pretty similar to our TexImage and GetTexImage
implementations.
The motivation behind this is to be able to use ReadPixels every frame and
still have at least 20 fps (or 60 fps with a powerful GPU and CPU)
instead of 0.5 fps.
Reviewed-by: Brian Paul <[email protected]>
Tested-by: Brian Paul <[email protected]>
|
| |
|
|
|
|
| |
Just use _mesa_get_fallback_texture() instead.
Reviewed-by: Jose Fonseca <[email protected]>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
needed
The default texture is used when the current fragment shader has texture
sample instructions but the user has not provided/bound a texture.
|
| |
|
|
|
|
|
|
| |
Calling glTexSubImage() or glTexImage() to replace texture data didn't
reliably cause pipe->set_sampler_texture() to get called so drivers didn't
always get notified of new texture data.
The st_texture_object->pt pointer doesn't always indicate changed data so
added a dirtyData field.
|
| |
|
|
|
| |
The effect of this mapping can be acheived by the state tracker and
setting up the pipe texture state pointers to incorporate its affects.
|
| |
|
|
| |
pipe->get_tex_surface() has to be used for access to texture image data.
|
| | |
|
| | |
|
| |
|
|
|
| |
We need to do these initializations before initializing the Mesa context
because context init involves creating texture/program/etc objects.
|
| |
|
