[Bug 21515] VENDOR_WINE vs VENDOR_ATI with xf86-video-ati

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=21515





--- Comment #13 from P.Panon <ppanon at shaw.ca>  2010-01-31 12:56:15 ---
Thanks Stefan. As you can see from comments #4 and #6, the GL renderer strings
for ATI drivers available in wined3d_guess_card() are:

OpenGL renderer string: Mesa DRI R300 (R300 4E45) 20090101 AGP 8x...
OpenGL renderer string: Mesa DRI R600 (RV670 9505) 20090101  TCL DRI2

So the first part (Mesa DRI R[36]00) can be used to identify the ATI open
source mesa drivers. It looks like (at least for the DRI600 driver) the part in
brackets could be used to identify the chip revision for better estimation of
chip capabilities. A list of ATI chipset codes are at

http://en.wikipedia.org/wiki/Comparison_of_ATI_graphics_processing_units#Radeon_R300_.289xxx.2C_X10xx.29_series

So I don't know if the R300 driver (current GL 1.5 conformance) offers enough
capabilities for DX9 or not. The R600 should. If you want to put together a
framework patch for testing the gl render string, then I'm willing to apply it
and test it on my end.

I was going to try to take a crack at doing this myself but I haven't quite
figured out how to see the TRACE() information results. I was trying to use set
+ win from http://www.winehq.org/docs/winedev-guide/dbg-commands, but when I
tried to do it in winedbg, it complained that it couldn't find debug symbols.

Wine-dbg>set + win
No symbols found for debug_options

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.