Am 12.10.2011 19:35, schrieb Christoph Bumiller:
> On 12.10.2011 19:17, Roland Scheidegger wrote:
>> Am 12.10.2011 16:31, schrieb Christoph Bumiller:
So do we need to go in and add PIPE_BIND_BLENDABLE to all of our
existing surface-create calls in the state tracker, etc?
>>> Well, th
On 12.10.2011 19:17, Roland Scheidegger wrote:
> Am 12.10.2011 16:31, schrieb Christoph Bumiller:
>>> So do we need to go in and add PIPE_BIND_BLENDABLE to all of our
>>> existing surface-create calls in the state tracker, etc?
>>>
>> Well, that depends on whether we want to put blending fallbacks
Am 12.10.2011 16:31, schrieb Christoph Bumiller:
>> So do we need to go in and add PIPE_BIND_BLENDABLE to all of our
>> existing surface-create calls in the state tracker, etc?
>>
>
> Well, that depends on whether we want to put blending fallbacks at the
> state tracker level (OpenGL is probably t
On 12.10.2011 16:12, Brian Paul wrote:
> On 10/10/2011 01:53 PM, Christoph Bumiller wrote:
>> This is required for d3d1x's CheckFormatSupport query.
>>
>> It also seems generally useful for state trackers, which could
>> choose alternative rendering paths or formats if blending would
>> come at a s
On 10/10/2011 01:53 PM, Christoph Bumiller wrote:
This is required for d3d1x's CheckFormatSupport query.
It also seems generally useful for state trackers, which could
choose alternative rendering paths or formats if blending would
come at a significant performance loss.
---
src/gallium/docs/s
This is required for d3d1x's CheckFormatSupport query.
It also seems generally useful for state trackers, which could
choose alternative rendering paths or formats if blending would
come at a significant performance loss.
---
src/gallium/docs/source/screen.rst |3 +++
src/gallium/include/pi
