[Bug 21886] Feature request: More detailed GL_RENDERER strings

[<bug...@fr...>]

http://bugs.freedesktop.org/show_bug.cgi?id=21886





--- Comment #5 from Corbin Simpson <Mos...@gm...>  2009-05-31 16:49:38 PST ---
Okay, so I thought about it a bit more.

1) We cannot actually provide fglrx-style strings from within the 3D stack. We
don't have the fine-grained data about which card the GPU's stuck on, and
unlike Intel (which only has about a dozen supported chipsets) or
nVidia/nouveau (where there's actually a VBIOS string with the card's marketing
name) there's no trivial way to craft it. So we have to report the chip family
instead.

2) Unlike fglrx (and, I assume, nvidia,) we don't register support for GL
extensions that we don't do in hardware. Classic Mesa has some pitfalls still
(GL_SELECT is one such unfun case) but for the most part, if an extension's
listed, it should be accelerated. So, for any driver that's !fglrx && !nvidia,
you shouldn't have to use GL_RENDERER much, because basing your detection on
GL_VERSION and the extension list should be sufficient.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.