mesa: call DrawBufferAllocate driver hook in update_framebuffer for windows-system FB
authorBoyan Ding <boyan.j.ding@gmail.com>
Sat, 14 Apr 2018 04:45:23 +0000 (14:45 +1000)
committerTimothy Arceri <tarceri@itsqueeze.com>
Tue, 24 Apr 2018 23:08:26 +0000 (09:08 +1000)
commit6695f9d5c5c94df080efc720ed532217618a28c3
treef829e9aad2172ef25f15d7b01fbe4494ce6df601
parent6ca09f3a608c10f6d2a9f80d2497ac1628188ac9
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@nuetzel-hh.de> (v2)
Reviewed-by: Brian Paul <brianp@vmware.com> (v2)
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99116
src/mesa/main/framebuffer.c