[Mesa-dev] RFC: Expose vertex/fragment progam limits in Mesa state tracker

[Marek Olšák]

On Thu, Apr 29, 2010 at 8:30 PM, Zack Rusin <zackr at vmware.com> wrote:

> It seems like all we'd really need is relate those things to
> the feature/api levels it exposes and document it.
>

Feature levels are a pretty bad match for D3D9-level chipsets since the
hardware is so divergent that you'd need a lot of them. You'd have at least
2 (I can come up with 3) levels just for r300g, at least two levels for
nvfx, and another two levels for the i9xx drivers, provided all these
drivers want to expose precisely every feature they can support. There is a
reason for having shader models sm2.0, sm2.0a, and sm2.0b. Moreover this
Microsoft idea is _absolutely_ useless for a GL driver. I like more the idea
of having util functions for deriving feature levels from a set of caps
rather than caps from feature levels.

-Marek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20100429/fde9749b/attachment.html>