Forget about the fun being had today on April Fools' Day with openSUSE / Gentoo / Arch / Debian supposedly merging to form the Centerbury Linux distribution, GNOME 3.0 being delayed until September, or hypothetical Linux disasters
as there is actually some serious
and important news: Marek Olšák has published his patch-set he wishes to push into Mesa master for OpenGL 3.0 floating-point textures and render-buffers support. He's pushing for this legally-iffy code to go into the mainline Mesa code-base but to block it by an opt-in --enable-texture-float
Marek Olšák, the well known community developer who's made significant contributions to Mesa / Gallium3D itself and particularly the open-source ATI drivers, has just published a set of six patches to the Mesa mailing list
. "This patch series adds the last pieces of ARB_texture_float support to Mesa and Gallium."
Here's the main part of the message:
The thing is Mesa and Gallium more or less already support float textures and renderbuffers in master. Gallium has full floating-point support in the interface and if it was a public API, people could just expose it and not care. There is clearly a need for a configure switch which can hide float renderbuffers from any interface, public or private, and driver developers should use such a switch.
So ARB_texture_float is mostly implemented in master. What's missing is the A/L/LA/I formats in Gallium, and the R/RG formats in the Mesa core, and some glue between Mesa and st/mesa.
I am proposing to merge all these patches and advertise ARB_texture_float if --enable-texture-float is used in configure.sh/autogen.sh. This is the same strategy the FreeType project had. If Linux distributors want ARB_texture_float (e.g. to get OpenGL 3), they should obtain the patent or find any other legal way around it, and then use the configure switch, but it's their and only their problem, not ours. By default, ARB_texture_float is disabled, so the Linux distributors not willing to support ARB_texture_float don't need to care.
BTW, this is not April Fools' prank.
It was in the beginning of March when Lucas Stach proposed merging Marek's floating-point/render-buffer branch
to mainline Mesa and to conceal it behind a --enable-patented
build option to move the legal burden from the Mesa developers and onto the distribution vendors and those compiling the code and distributing the binary packages.
There was interest in merging the work
, but ultimately it didn't happen. This also then brought another proposal of merging the S3TC support to Mesa
and hiding it behind a similar build switch. The difference though between the S3TC and floating-point / render-buffer work is that the the S3 Texture Compression work can live relatively cleanly in an external library that's dynamically loaded by Mesa. The floating-point / render-buffer work does much better living directly within the core.
While it didn't get merged
then, Marek himself is now bringing the matter to the mailing list himself and showing the six patches in particular that would need to be merged rather than just trying to pull his floating branch.
Hopefully now we will see GL_ARB_texture_float merged to master, albeit it will be disabled by default. This would be another step forward with Mesa / Gallium3D finally catching up to the latest OpenGL 3.x/4.x specifications. As far as what this means, with the very latest Mesa 7.11-devel / Gallium 0.4 development Git code and floating-point support enabled, Unigine Heaven can now run on Gallium3D
. This impressive technology demo may now function, but how it performance is still less than desirable.