diff options
author | Boyan Ding <[email protected]> | 2018-04-14 14:45:23 +1000 |
---|---|---|
committer | Timothy Arceri <[email protected]> | 2018-04-25 09:08:26 +1000 |
commit | 6695f9d5c5c94df080efc720ed532217618a28c3 (patch) | |
tree | f829e9aad2172ef25f15d7b01fbe4494ce6df601 /src/amd | |
parent | 6ca09f3a608c10f6d2a9f80d2497ac1628188ac9 (diff) |
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 <[email protected]> (v2)
Reviewed-by: Brian Paul <[email protected]> (v2)
Reviewed-by: Marek Olšák <[email protected]>
Reviewed-by: Ian Romanick <[email protected]>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99116
Diffstat (limited to 'src/amd')
0 files changed, 0 insertions, 0 deletions