- Original Message -
> On 12/09/2011 01:58 AM, Jose Fonseca wrote:
> > - Original Message -
> >> On Fri, Dec 9, 2011 at 2:02 PM, Chia-I Wu wrote:
> >>> On Thu, Dec 8, 2011 at 10:00 PM, wrote:
> From: José Fonseca
>
> It sets the wrong values (GL_XXX_LEFT instead o
On 12/09/2011 01:58 AM, Jose Fonseca wrote:
- Original Message -
On Fri, Dec 9, 2011 at 2:02 PM, Chia-I Wu wrote:
On Thu, Dec 8, 2011 at 10:00 PM, wrote:
From: José Fonseca
It sets the wrong values (GL_XXX_LEFT instead of GL_XXX), and no
other
Mesa driver does this, given that Mesa
- Original Message -
> On Fri, Dec 9, 2011 at 2:02 PM, Chia-I Wu wrote:
> > On Thu, Dec 8, 2011 at 10:00 PM, wrote:
> >> From: José Fonseca
> >>
> >> It sets the wrong values (GL_XXX_LEFT instead of GL_XXX), and no
> >> other
> >> Mesa driver does this, given that Mesa sets the right dr
On Fri, Dec 9, 2011 at 2:02 PM, Chia-I Wu wrote:
> On Thu, Dec 8, 2011 at 10:00 PM, wrote:
>> From: José Fonseca
>>
>> It sets the wrong values (GL_XXX_LEFT instead of GL_XXX), and no other
>> Mesa driver does this, given that Mesa sets the right draw/read buffers
>> provided the Mesa visual ha
On Thu, Dec 8, 2011 at 10:00 PM, wrote:
> From: José Fonseca
>
> It sets the wrong values (GL_XXX_LEFT instead of GL_XXX), and no other
> Mesa driver does this, given that Mesa sets the right draw/read buffers
> provided the Mesa visual has the doublebuffer flag filled correctly
> which is the c
On 12/08/2011 07:00 AM, jfons...@vmware.com wrote:
From: José Fonseca
It sets the wrong values (GL_XXX_LEFT instead of GL_XXX), and no other
Mesa driver does this, given that Mesa sets the right draw/read buffers
provided the Mesa visual has the doublebuffer flag filled correctly
which is the ca
From: José Fonseca
It sets the wrong values (GL_XXX_LEFT instead of GL_XXX), and no other
Mesa driver does this, given that Mesa sets the right draw/read buffers
provided the Mesa visual has the doublebuffer flag filled correctly
which is the case.
---
src/mesa/state_tracker/st_manager.c | 64