On 01/04/2016 07:22 PM, Ilia Mirkin wrote:
> Sure, no problem. Do you think you'll have time to look at it in the
> next day or two though?
Yes. I'll review it on Thursday.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
On 12/31/2015 11:55 AM, Ilia Mirkin wrote:
> This is optional for now in the transition period, but optimally all
> backends that support indirect draws would switch over to it and we can
> remove the support for indirect in the "regular" draw function.
>
> This should allow a backend to properly
On Mon, Jan 4, 2016 at 10:10 PM, Ian Romanick wrote:
> On 12/31/2015 11:55 AM, Ilia Mirkin wrote:
>> This is optional for now in the transition period, but optimally all
>> backends that support indirect draws would switch over to it and we can
>> remove the support for
[adding Ian and Ken, who may or may not be interested]
I'd like to push this out in the next couple of days (along with my
ARB_indirect_parameters series), but I'd really like to get an ack
from someone on the Intel team that such an interface would be
acceptable to them. You can see the full
Acked-by: Marek Olšák
On Thu, Dec 31, 2015 at 8:55 PM, Ilia Mirkin wrote:
> This is optional for now in the transition period, but optimally all
> backends that support indirect draws would switch over to it and we can
> remove the support for indirect
Thanks! I'd also like to get an ack from someone on the Intel crew as
well to make sure this interface will work for them as well.
On Fri, Jan 1, 2016 at 6:49 AM, Marek Olšák wrote:
> Acked-by: Marek Olšák
>
> On Thu, Dec 31, 2015 at 8:55 PM, Ilia Mirkin
This is optional for now in the transition period, but optimally all
backends that support indirect draws would switch over to it and we can
remove the support for indirect in the "regular" draw function.
This should allow a backend to properly support ARB_multi_draw_indirect
and