| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
XMesaContext has an st_context * which contains a mesa context.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
program concatenation.
|
|
fragment shaders through llvm.
|
|
intelCopyBuffer() is now intelDisplayBuffer(): it displays the given surface
in the on-screen window.
Added a pipe_surface parameter to winsys->flush_frontbuffer().
Front buffer rendering/flushing actually works now.
But, we should only allocate the front surface on demand...
|
|
context.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Start lifting Mesa stuff up out of winsys/driver code.
|
|
|
|
|
|
glDrawPixels.
|
|
do pixel transfer in the fragment program.
|
|
|
|
|
|
|
|
|
|
Basic code for PixelTranslfer ops and glDrawPixels works now.
A pixel transfer program is generated and combined with the current
fragment shader.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Previously, we set _NEW_PIXEL and _NEW_COLOR in these functions, respectively.
That correponds to the GL attribute groups, but doesn't make much sense
otherwise. This could improve validation efficiency in a few places too.
It looks like all the drivers are already checking for _NEW_BUFFERS in the
right places (since that's the bit for FBO state) so we can trim out
_NEW_PIXEL and _NEW_COLOR at any time.
|
|
|
|
|
|
For generating fragment programs which implement pixel transfer ops.
|
|
Enables immediates by default in the TGSI translation code
and adds code handling it in llvm tgsi translation.
|
