This patch adds direct and indirect rendering support for
GLX_MESA_copy_sub_buffer. Intel, r200 and r300 drivers are the only
drivers I've implemented support for so far. I've only tried the intel
implementation and that seems to be working OK. I've attached a patch
for CVS head and one for 6.4.2.
On Mon, 2006-03-13 at 18:28 +0100, Michel Dänzer wrote:
On Mon, 2006-03-13 at 18:04 +0100, David Reveman wrote:
This patch adds direct and indirect rendering support for
GLX_MESA_copy_sub_buffer. Intel, r200 and r300 drivers are the only
drivers I've implemented support for so far.
It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Reveman wrote:
This patch adds direct and indirect rendering support for
GLX_MESA_copy_sub_buffer. Intel, r200 and r300 drivers are the only
drivers I've implemented support for so far. I've only tried the intel
implementation and that seems
On Mon, 2006-03-13 at 14:04 -0800, Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Reveman wrote:
On Mon, 2006-03-13 at 10:45 -0800, Ian Romanick wrote:
David Reveman wrote:
This patch adds direct and indirect rendering support for
GLX_MESA_copy_sub_buffer.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Reveman wrote:
I thought that a call to SwapBuffers would always make the content of
the back buffer undefined. So if you want to use CopySubBufferMESA for
quickly repainting part of the buffer as the in the spec, you would
never use
Hi,
I recently tried to compile the Mesa fbdev/DRI drivers. Since I do not
have X installed, this seemed to be exactly what I needed.
Although the Mesa fbdev/DRI drivers do not require X, it seems that some
X utilities and libs are at least required during the compilation
process. I
I recently tried to compile the Mesa fbdev/DRI drivers. Since I do not have X
installed, this seemed to be exactly what I needed.
Although the Mesa fbdev/DRI drivers do not require X, it seems that some X
utilities and libs are at least required during the compilation process. I
encountered
