[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 #63 from Stefan Dösinger <stefandoesinger at gmx.at>  2010-02-10 15:16:46 ---
I recommend to keep track of the other bugs in a separate bug report to make
following each issue easier. Beyond that I am opposed to put a np2-disable
quirk for mesa r600+ cards into the Wine git tree because the Mesa drivers are
under heavy development and such quirks tend to hurt in the long run. Peeking
around at what changes the driver behavior and documenting this in a bug report
is a good thing though.

There are no written rules towards which quirks are accepted into git, but it
goes somewhat like this: A quirk is ok if:

* It is using an unspecified driver behavior to our advantage(e.g. the specular
color quirk or the normalized texrect quirk)
* There's a driver bug that is unlikely to get fixed anytime soon(e.g. legacy
proprietary driver, or Apple drivers) and it hurts a wide range of apps(e.g.
NVTS disable quirk on OSX)
* A genuine hardware limitation that cannot be adequately queried from GL(NP2
texture disable on Geforce FX, NP2 texture disable on r300-r500)
* A driver bug that causes a kernel panic or X server crash when running the
wine tests(Otherwise people are afraid of running "make test"). E.g. point
sprite quirk on fglrx.

Since it is comparably easy to get an open source driver fixed we try to avoid
quirks for them, except if they're in the last category(People are often
running old drivers, working on a non-d3d area of wine, run "make test" and get
a kernel panic)

-- 
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.