On 2010-04-29 18.23, Jakob Bornecrantz wrote:
On 2010-04-29 17.11, Keith Whitwell wrote:
Jakob,

A couple of these are a bit misleading - DX10&   DX11 aren't fully
supportable without further changes&   extensions to gallium, so it seems
misleading to have these ever return true - at least until those changes
are done.

Would it make sense to have a UTIL_CHECK_NONIMPLEMENTED or similar that
always fails, which we can remove once proper support is in gallium?


Right added a unimplemented check and comments to clarify.

Even tho those list are just demos it would be nice if anybody who has
more time then me would update them to be more extensive of the required
caps for different APIs and extensions.

So the plan was to commit these changes and write a small email follow up, but it took a bit longer then planned to write the code and apply input from people and suddenly it was beer o clock, so anyways here it is:

The goal of the code was to provide a way to express a set of requirments for a given feature/extension or version of API. But just as important was the readability of this list for driver developers trying to get a good overview of which features to implement for a given extension or API.

So regarding the demo tables, I tried to express a feature level table from the DX11 documentation[1]. But I didn't finish it. I had a bit to match up all the features against Gallium features. If somebody has a itch to finish this please go ahead, this is pretty much a janitorial task.

The OpenGL case is a bit more difficult to figure out since the code that determines which OpenGL version to expose is spread across st_extensions.c and main/extensions.c, again another janitorial task.

On a unrelated note Marek, if you follow the link you will see that Microsoft divided DX9 into 3 levels.

Cheers Jakob.

[1] http://msdn.microsoft.com/en-us/library/ff476876(v=VS.85).aspx
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to