-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/16/2011 10:26 AM, Chad Versace wrote:
> I've observed mysterious behaviour when writing to intel's stencil
> buffer through a memory mapped pointer. It's seems that the hardware
> fails to recognize that the writes ever occurred. (Writes via
> re
On Thu, Jun 16, 2011 at 1:26 PM, Chad Versace wrote:
> On 06/16/2011 08:01 AM, Alex Deucher wrote:
>> On Wed, Jun 15, 2011 at 9:09 PM, Chad Versace wrote:
>>> If a renderbuffer wraps multiple renderbuffers, then Unwrapped points to
>>> the them.
>>>
>>> For example, if hardware requires separate
On 06/16/2011 08:01 AM, Alex Deucher wrote:
> On Wed, Jun 15, 2011 at 9:09 PM, Chad Versace wrote:
>> If a renderbuffer wraps multiple renderbuffers, then Unwrapped points to
>> the them.
>>
>> For example, if hardware requires separate depth and stencil buffers
>> (X8_Z24 and S8), then glRenderbu
On Wed, Jun 15, 2011 at 9:09 PM, Chad Versace wrote:
> If a renderbuffer wraps multiple renderbuffers, then Unwrapped points to
> the them.
>
> For example, if hardware requires separate depth and stencil buffers
> (X8_Z24 and S8), then glRenderbufferStorage(GL_DEPTH24_STENCIL8) may
> create a fak
If a renderbuffer wraps multiple renderbuffers, then Unwrapped points to
the them.
For example, if hardware requires separate depth and stencil buffers
(X8_Z24 and S8), then glRenderbufferStorage(GL_DEPTH24_STENCIL8) may
create a fake S8_Z24 renderbuffer for which Unwrapped[BUFFER_DEPTH] and
Unwra
