On Fri, Dec 15, 2017 at 1:08 PM, Nicolai Hähnle wrote:
> On 15.12.2017 12:37, Rob Clark wrote:
>>
>> On Fri, Dec 15, 2017 at 4:41 AM, Nicolai Hähnle
>> wrote:
>>>
>>> On 15.12.2017 00:56, Rob Clark wrote:
On Wed, Dec 6, 2017 at
Nicolai Hähnle writes:
> On 15.12.2017 12:37, Rob Clark wrote:
>> On Fri, Dec 15, 2017 at 4:41 AM, Nicolai Hähnle
>> wrote:
>>> On 15.12.2017 00:56, Rob Clark wrote:
On Wed, Dec 6, 2017 at 3:31 PM, Ian Romanick
On 15.12.2017 12:37, Rob Clark wrote:
On Fri, Dec 15, 2017 at 4:41 AM, Nicolai Hähnle wrote:
On 15.12.2017 00:56, Rob Clark wrote:
On Wed, Dec 6, 2017 at 3:31 PM, Ian Romanick wrote:
On 12/05/2017 08:25 AM, Ilia Mirkin wrote:
On Tue, Dec 5,
On Fri, Dec 15, 2017 at 4:41 AM, Nicolai Hähnle wrote:
> On 15.12.2017 00:56, Rob Clark wrote:
>>
>> On Wed, Dec 6, 2017 at 3:31 PM, Ian Romanick wrote:
>>>
>>> On 12/05/2017 08:25 AM, Ilia Mirkin wrote:
On Tue, Dec 5, 2017 at 8:18 AM,
On 15.12.2017 00:56, Rob Clark wrote:
On Wed, Dec 6, 2017 at 3:31 PM, Ian Romanick wrote:
On 12/05/2017 08:25 AM, Ilia Mirkin wrote:
On Tue, Dec 5, 2017 at 8:18 AM, Emil Velikov wrote:
Hi Rob,
On 5 December 2017 at 12:54, Rob Clark
On Wed, Dec 6, 2017 at 3:31 PM, Ian Romanick wrote:
> On 12/05/2017 08:25 AM, Ilia Mirkin wrote:
>> On Tue, Dec 5, 2017 at 8:18 AM, Emil Velikov
>> wrote:
>>> Hi Rob,
>>>
>>> On 5 December 2017 at 12:54, Rob Clark wrote:
On Wed, Dec 6, 2017 at 3:31 PM, Ian Romanick wrote:
> On 12/05/2017 08:25 AM, Ilia Mirkin wrote:
>> On Tue, Dec 5, 2017 at 8:18 AM, Emil Velikov
>> wrote:
>>> Hi Rob,
>>>
>>> On 5 December 2017 at 12:54, Rob Clark wrote:
On 12/05/2017 08:25 AM, Ilia Mirkin wrote:
> On Tue, Dec 5, 2017 at 8:18 AM, Emil Velikov wrote:
>> Hi Rob,
>>
>> On 5 December 2017 at 12:54, Rob Clark wrote:
>>> This is a bit sad/annoying. But with current GPU firmware (at least on
>>> a5xx) we
On Tue, Dec 5, 2017 at 8:18 AM, Emil Velikov wrote:
> Hi Rob,
>
> On 5 December 2017 at 12:54, Rob Clark wrote:
>> This is a bit sad/annoying. But with current GPU firmware (at least on
>> a5xx) we can support both draw-indirect and base-instance.
Hi Rob,
On 5 December 2017 at 12:54, Rob Clark wrote:
> This is a bit sad/annoying. But with current GPU firmware (at least on
> a5xx) we can support both draw-indirect and base-instance. But we can't
> support draw-indirect with a non-zero base-instance specified. So add
On Tue, Dec 5, 2017 at 8:02 AM, Ilia Mirkin wrote:
> On Tue, Dec 5, 2017 at 7:54 AM, Rob Clark wrote:
>> This is a bit sad/annoying. But with current GPU firmware (at least on
>> a5xx) we can support both draw-indirect and base-instance. But we can't
On Tue, Dec 5, 2017 at 7:54 AM, Rob Clark wrote:
> This is a bit sad/annoying. But with current GPU firmware (at least on
> a5xx) we can support both draw-indirect and base-instance. But we can't
> support draw-indirect with a non-zero base-instance specified. So add a
This is a bit sad/annoying. But with current GPU firmware (at least on
a5xx) we can support both draw-indirect and base-instance. But we can't
support draw-indirect with a non-zero base-instance specified. So add a
driconf option to hide the extension from games that are known to use
both.
13 matches
Mail list logo