Re: [Mesa-dev] [PATCH] mesa: Allow glReadBuffer(GL_NONE) for winsys framebuffers.

2012-12-19 Thread Paul Berry
On 19 December 2012 16:36, Ian Romanick wrote: > On 12/19/2012 01:07 PM, Paul Berry wrote: > >> Previously, Mesa code assumed that glReadBuffer(GL_NONE) was only >> valid for user-created framebuffer objects. However, the spec is >> quite clear that is should also be valid for the default frameb

Re: [Mesa-dev] [PATCH] mesa: Allow glReadBuffer(GL_NONE) for winsys framebuffers.

2012-12-19 Thread Ian Romanick
On 12/19/2012 01:07 PM, Paul Berry wrote: Previously, Mesa code assumed that glReadBuffer(GL_NONE) was only valid for user-created framebuffer objects. However, the spec is quite clear that is should also be valid for the default framebuffer. From section 18.2.1 ("Obtaining Pixels from the Fram

Re: [Mesa-dev] [PATCH] mesa: Allow glReadBuffer(GL_NONE) for winsys framebuffers.

2012-12-19 Thread Eric Anholt
Paul Berry writes: > Previously, Mesa code assumed that glReadBuffer(GL_NONE) was only > valid for user-created framebuffer objects. However, the spec is > quite clear that is should also be valid for the default framebuffer. > From section 18.2.1 ("Obtaining Pixels from the Framebuffer") of the

[Mesa-dev] [PATCH] mesa: Allow glReadBuffer(GL_NONE) for winsys framebuffers.

2012-12-19 Thread Paul Berry
Previously, Mesa code assumed that glReadBuffer(GL_NONE) was only valid for user-created framebuffer objects. However, the spec is quite clear that is should also be valid for the default framebuffer. >From section 18.2.1 ("Obtaining Pixels from the Framebuffer") of the GL 4.3 spec: "When REA