[Mesa-dev] [Bug 99116] Wine DirectDraw programs showing only a blackscreen when using Mesa Gallium drivers
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Apr 24 23:14:22 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=99116
Timothy Arceri <t_arceri at yahoo.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #19 from Timothy Arceri <t_arceri at yahoo.com.au> ---
Should be fixed by:
commit 6695f9d5c5c94df080efc720ed532217618a28c3
Author: Boyan Ding <boyan.j.ding at gmail.com>
Date: Sat Apr 14 14:45:23 2018 +1000
mesa: call DrawBufferAllocate driver hook in update_framebuffer for
windows-system FB
When draw buffers are changed on a bound framebuffer, DrawBufferAllocate()
hook should be called. However, it is missing in update_framebuffer with
window-system framebuffer, in which FB's draw buffer state should match
context state, potentially resulting in a change.
Note: This is needed because gallium delays creating the front buffer,
i965 works fine without this change.
V2 (Timothy Arceri):
- Rebased on merged/simplified DrawBuffer driver function
- Move DrawBuffer call outside fb->ColorDrawBuffer[0] !=
ctx->Color.DrawBuffer[0] check to make piglit pass.
v3 (Timothy Arceri):
- Call new DrawBuffaerAllocate() driver function.
Tested-by: Dieter Nützel <Dieter at nuetzel-hh.de> (v2)
Reviewed-by: Brian Paul <brianp at vmware.com> (v2)
Reviewed-by: Marek Olšák <marek.olsak at amd.com>
Reviewed-by: Ian Romanick <ian.d.romanick at intel.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99116
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180424/a500050c/attachment-0001.html>
More information about the mesa-dev
mailing list