http://bugs.winehq.org/show_bug.cgi?id=21515
--- Comment #94 from Henri Verbeet hverbeet@gmail.com 2010-02-26 09:25:16 --- (In reply to comment #92)
I'm not sure this is a good idea, as Mesa and Gallium aren't the same drivers and may require different quirks in the future. But this is probably better answered by somebody with knowledge of the internals of Wine's D3D implementation and driver handling. In case your proposition is viable, I'm happy to try to work it into the current patch series (or add it on top of that).
We can split classic Mesa and Gallium if needed, but the main use of this code should be for reporting the right card and driver info back to the application. We also have plenty of quirks that use this information, but there's a strong preference to test actual behaviour for quirks instead of depending on the detected card/driver.