Cross-regressions between wine and mesa: how to handle them?
b7.10110111 at gmail.com
Mon Mar 17 06:53:20 CDT 2014
More than a month has passed since the bug report, and Mesa devs
haven't said anything. What should my further actions be? I suppose
some of the following:
1. Wait more
2. File a bug at winehq and hope that something could be done as a
3. Not rely on this being fixable and tell all users with i915 and
similar chips to patch either wine or mesa, or maybe use some registry
overrides in wine (UseGLSL and the like)
4. Something better?
On Sun, Feb 2, 2014 at 5:34 PM, Ruslan Kabatsayev <b7.10110111 at gmail.com> wrote:
> On Fri, Jan 31, 2014 at 1:47 PM, Henri Verbeet <hverbeet at gmail.com> wrote:
>> On 31 January 2014 09:45, Ruslan Kabatsayev <b7.10110111 at gmail.com> wrote:
>>> Without glPointParameter() calls I don't have those errors after
>>> "[snip repeating messages]", but still do have CopyTexSubImage ones
>>> (although I didn't notice such a serious slowdown as was before; and
>>> these have also been before bisected wine commit).
>> If the CopyTexSubImage ones aren't repeating after initial loading,
>> they may be from the wined3d GL quirk detection code or the FBO caps
>> detection code, in which case they would be harmless.
> They indeed don't repeat after loading. They appear after this commit:
> 7b0ba5153f3e42f31b922e5eb997d5e1d0cb44d4 is the first bad commit
> commit 7b0ba5153f3e42f31b922e5eb997d5e1d0cb44d4
> Author: Matteo Bruni <mbruni at codeweavers.com>
> Date: Thu Nov 3 15:26:36 2011 +0100
> wined3d: Test more thoroughly for post-pixelshader blending
> support, try on more texture formats.
> :040000 040000 4ccfbad52a0797cdd96f4efccafeac45c6ce688a
> 026bd6e57c4cbbf8c906eddcb43527ffdbe233f7 M dlls
More information about the wine-devel