Ian Romanick wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Is there any sort of documentation available to help developers port
>drivers to the new TTM interfaces? It would be really nice to get the
>r200 and r300 drivers ported over. Being able to get VBOs in r200 and
>eliminate the
Thanks
No, it’s not, I’ve traced
down the SwapBuffer function , what the swap does is flushing all the commands
in the buffer and rasterizing the vertices to pixels.
But I didn’t find anything
related displaying those pixels to the screen.
I wonder whether this unknown
displaying functio
I was building Mesa-6.5.1 and got the following error:
gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
-I../../../../../include -I../../../../../include/GL/internal
-I../../../../../src/mesa -I../../../../../src/mesa/main
-I../../../../../src/mesa/glapi -I../../../../../src/mesa/m
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=473
[EMAIL PROTECTED] changed:
What|Removed |Added
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there any sort of documentation available to help developers port
drivers to the new TTM interfaces? It would be really nice to get the
r200 and r300 drivers ported over. Being able to get VBOs in r200 and
eliminate the GARTSize cruft in r300 woul
Jin, Gordon wrote:
Thomas Hellstr?m wrote:
Hi!
We're about to merge the texmem-0-3 branch with the Mesa trunk. This
will currently only affect the i915 driver.
To make the new i915 driver work after the merge one has to obtain the
latest xserver git, the latest xf86-video-intel g
