On 31 October 2013 05:38, Rogovin, Kevin wrote:
>
>
> >> but I do not quite follow the second upload; what
> >> is the magicks going on with batch->state_batch_offset and for that
> matter
> >> batch->bo->size ??
>
> >This is stack and heap model for batchbuffer submission. Direct state,
> which
On 31 October 2013 02:22, Rogovin, Kevin wrote:
>Hi,
>
> Thankyou for the detailed answer, and now I have still more questions:
>
> > No. do_flush_locked() (which is called by intel_batch_buffer_flush())
> follows that by calling either drm_intel_bo_mrb_exec() or
> drm_intel_gem_bo_context
On Thursday, October 31, 2013 12:38:37 PM Rogovin, Kevin wrote:
> >> but I do not quite follow the second upload; what
> >> is the magicks going on with batch->state_batch_offset and for that
> >> matter
> >> batch->bo->size ??
> >
> >This is stack and heap model for batchbuffer submission. Direct
>> but I do not quite follow the second upload; what
>> is the magicks going on with batch->state_batch_offset and for that matter
>> batch->bo->size ??
>This is stack and heap model for batchbuffer submission. Direct state, which
>is usually composed of the commands, is allocated at the beginni
On Thursday, October 31, 2013 09:22:23 AM Rogovin, Kevin wrote:
> but I do not quite follow the second upload; what
> is the magicks going on with batch->state_batch_offset and for that matter
> batch->bo->size ??
This is stack and heap model for batchbuffer submission. Direct state, which
is us
Hi,
Thankyou for the detailed answer, and now I have still more questions:
> No. do_flush_locked() (which is called by intel_batch_buffer_flush())
> follows that by calling either drm_intel_bo_mrb_exec() or
> drm_intel_gem_bo_context_exec(). That's what > causes the batch to be queued
> for
On 30 October 2013 11:55, Rogovin, Kevin wrote:
> Hello all,
>
> I've got some questions and I would appreciate if anyone could help me
> out. Here goes:
>
> I've been digging through brw_try_draw_prims(), and trying to figure out
> what it is doing, so far this is what I see:
>
> 1) it is ess
Hello all,
I've got some questions and I would appreciate if anyone could help me out.
Here goes:
I've been digging through brw_try_draw_prims(), and trying to figure out what
it is doing, so far this is what I see:
1) it is essentially called each time a non-degenerate "real drawing"
glDr
