OpenGL ES 1.1/2.0 State Trackers For Gallium3D

[phoronix]

Phoronix: OpenGL ES 1.1/2.0 State Trackers For Gallium3D

Just minutes after announcing Mesa 7.5 Release Candidate 2, Brian Paul has announced that he is in the process of pushing out Gallium3D state trackers for OpenGL ES 1.1 and OpenGL ES 2.0. These two new state trackers for this forthcoming Linux graphics architecture are coming just two weeks after an OpenVG state tracker was released for accelerating this other Khronos API.The OpenGL ES 1.1 and ES 2.0 state trackers each provide a subset of Mesa plus other ES-specific bits...

http://www.phoronix.com/vr.php?view=NzI3Mw

[ethana2]

We need Direct3D 9 and 10 state trackers also, so the WINE folks can actually work on WINE instead of trying to rewrite all of directX in OpenGL.

[Pfanne]

wasnt there a rumor about an internal direct3d tracker?

[Craig73]

We need Direct3D 9 and 10 state trackers also, so the WINE folks can actually work on WINE instead of trying to rewrite all of directX in OpenGL.

I understood that the WINE developers felt their current approach was the best path. (but somehow I suspect someone will attempt this regardless)

[dashcloud]

So are these state trackers only useful for embedded devices, or would other drivers benefit from them as well? (possibly the radeon drivers?)

[TechMage89]

Any Gallium3D driver would be able to use these state trackers, but applications using OpenGL ES are primarily applications targeted at mobile devices.

[Zhick]

Now we just need to wait for the OpenCL state tracker and an OpenGL 3.1 state tracker.

And for a driver that actually makes use of any of these shiny state trackers. :P

[Pfanne]

im interessted in how long it did take them to write this opengl es statetracker and how long it would take to write a tracker for opengl3.0 oder direct3d9 or something

[bridgman]

According to Brian's announcement the GL ES state tracker was a subset of the existing Mesa code with some additional ES-specific bits added, so the effort would not really be comparable to writing a new tracker (like D3D9) from scratch.

More info at : http://cgit.freedesktop.org/mesa/mes...ml?h=opengl-es

OpenGL 3.0 is probably somewhere in between since it can build on top of the existing Mesa GL 2.x state tracker code.

EDIT - Zack mentioned plans for TG/VMware to work on GL 3.1 support :

http://zrusin.blogspot.com/2009/05/opengl-es.html

[whizse]

And for a driver that actually makes use of any of these shiny state trackers. :P

It would be interesting if Phoronix would do an article with an overview of the status of the drivers, and what kind of plans/estimations the developers of the different drivers (intel/ati/nouveau/via) have for gallium support.