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

wine-bugs at winehq.org wine-bugs at winehq.org
Fri Feb 5 03:45:13 CST 2010


--- Comment #30 from Stefan Dösinger <stefandoesinger at gmx.at>  2010-02-05 03:45:08 ---
> Different drivers for the same hardware are likely to have fewer differences
> than different drivers on different hardware, so whats wrong with using
> VENDOR_ATI with AMD cards regardless of driver?
We work around a few fglrx bugs, and we don't want to apply those workarounds
to Mesa when Mesa doesn't have the bugs, and vice versa. So we want to report
VENDOR_ATI to the game, but we also have to keep track of the driver vendor.

> If not, how can one of us write an acceptable patch? ie. considering just
> duplicating (more or less) all the strstr calls from under VENDOR_ATI to
> VENDOR_MESA is unlikely to be an acceptable solution? Should
> wined3d_guess_vendor() and wined3d_guess_card() be re-written with something
> like libpci for detection?
libpci is not an option because it is not portable to e.g. OSX.

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.

More information about the wine-bugs mailing list