http://bugs.freedesktop.org/show_bug.cgi?id=21886
Summary: Feature request: More detailed GL_RENDERER strings
Product: Mesa
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Mesa core
AssignedTo: [email protected]
ReportedBy: [email protected]
Currently the r300 driver(just an example) reports this vendor and renderer
info:
OpenGL vendor string: DRI R300 Project
OpenGL renderer string: Mesa DRI R300 20090101 x86/MMX/SSE2 TCL DRI2
OpenGL version string: 1.4 Mesa 7.6-devel
Wine uses the vendor and renderer strings to make a rough guess which card is
in use to report a PCI vendor and device ID to D3D apps. The renderer string is
the same for all cards run by the r300 driver, which makes it hard to separate
a radeon 9500 from a radeon X1950.
We know that GL apps should not look at the strings to make decisions, but we
have to do this for a few reasons:
1) Very few D3D apps are broken and do use the PCI IDs and not the capability
flags to select render paths(Command & Conquers generals)
2) user reporting: Users get confused if they have a e.g. X1600 in their
system, and their game pretends it is running on a 9500. We often get false bug
reports where people think this misdetection causes their app to fail.
3) Some games don't make vital decisions based on the IDs, but enable / disable
extra features. E.g. Age of Empires 3 enables very high shader support on
Geforce 7 cards(even low level ones), but disables that on Geforce 6 cards(even
high level ones). There's no technical reason to do that, but the game does
it(I guess some ad deal with Nvidia)
4) We don't want to look at the lspci output because it is not portable, and we
may report a card that does not match our features. Currently Mesa does not
support GLSL on r300 cards, so Wine only offers 1.x shaders(that will change).
So we can't report a Radeon 9500 at the moment because the capabilities do not
match that card. (We use the GL extensions to make broad guess and the vendor
string for a fine-grained selection).
>From the current info mesa provides we can find out that we have an ATI
card(search for "R300), but we cannot separate r300, r400 and r500 cards, or
subtypes or mobility cards.
A renderer string like the one fglrx reports would be more helpful:
OpenGL renderer string: ATI Mobility Radeon X1600
I don't need exactly the same format, just something like "Mobility Radeon
X1600" on that card in the string.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
