[Mesa-dev] Question about min_index/max_index calculation

Connor Abbott cwabbott0 at gmail.com
Sat Mar 24 22:11:29 UTC 2018


On Sat, Mar 24, 2018 at 6:00 PM, Jason Ekstrand <jason at jlekstrand.net> wrote:
> On Sat, Mar 24, 2018 at 2:27 PM, Marek Olšák <maraeo at gmail.com> wrote:
>>
>> On Sat, Mar 24, 2018 at 1:36 PM, Connor Abbott <cwabbott0 at gmail.com>
>> wrote:
>>>
>>> If Gallium was being lazy and not
>>> specifying the bounds for internal shaders, that needs to be fixed for
>>> the HW to work properly.
>>
>>
>> I don't understand the sentence. Shaders don't interact with vertex
>> indices. I also don't like the word "lazy". The proper expression is "saving
>> time".
>
>
> I figured he meant for things like u_blitter.  But why those things would be
> using an index buffer is beyond me...

Yeah, that was just speculation. I just meant to explain why Mali
might require the min/max index up-front, unlike other HW (AFAIK). I'm
certainly no expert when it comes to Gallium, and I don't have the
hardware to reproduce the problem.


More information about the mesa-dev mailing list