- Original Message -
> Am 07.06.2013 16:55, schrieb Jose Fonseca:
> >
> >
> > - Original Message -
> >> Am 06.06.2013 03:15, schrieb Brian Paul:
> >>> Reviewed-by: Brian Paul
> >>>
> >>> Just two minor nits below.
> >>>
> >>>
> >>> On 06/05/2013 05:44 PM, srol...@vmware.com wro
Am 07.06.2013 16:55, schrieb Jose Fonseca:
>
>
> - Original Message -
>> Am 06.06.2013 03:15, schrieb Brian Paul:
>>> Reviewed-by: Brian Paul
>>>
>>> Just two minor nits below.
>>>
>>>
>>> On 06/05/2013 05:44 PM, srol...@vmware.com wrote:
From: Roland Scheidegger
Mostly j
- Original Message -
> Am 06.06.2013 03:15, schrieb Brian Paul:
> > Reviewed-by: Brian Paul
> >
> > Just two minor nits below.
> >
> >
> > On 06/05/2013 05:44 PM, srol...@vmware.com wrote:
> >> From: Roland Scheidegger
> >>
> >> Mostly just make sure the layer parameter gets passed t
Am 06.06.2013 03:15, schrieb Brian Paul:
> Reviewed-by: Brian Paul
>
> Just two minor nits below.
>
>
> On 06/05/2013 05:44 PM, srol...@vmware.com wrote:
>> From: Roland Scheidegger
>>
>> Mostly just make sure the layer parameter gets passed through to the
>> right
>> places (and get clamped,
Reviewed-by: Brian Paul
Just two minor nits below.
On 06/05/2013 05:44 PM, srol...@vmware.com wrote:
From: Roland Scheidegger
Mostly just make sure the layer parameter gets passed through to the right
places (and get clamped, can do this at setup time), fix up clears to
clear all layers and
From: Roland Scheidegger
Mostly just make sure the layer parameter gets passed through to the right
places (and get clamped, can do this at setup time), fix up clears to
clear all layers and disable opaque optimization. Luckily don't need to
touch the jitted code.
(Clears invoked via pipe's clear
