On Wed, 2009-09-23 at 02:23 -0700, Dave Airlie wrote:
> > > > So in mesa for swtcl cases we emit vertices to DMA, and set a driver
> > > > internal dma.flush hook, we also set
> > > > ctx->Driver.NeedFlush |= FLUSH_STORED_VERTICES;
> > > >
> > > > The driver has its FlushVertices pointed at the vb
> > > So in mesa for swtcl cases we emit vertices to DMA, and set a driver
> > > internal dma.flush hook, we also set
> > > ctx->Driver.NeedFlush |= FLUSH_STORED_VERTICES;
> > >
> > > The driver has its FlushVertices pointed at the vbo_exec_FlushVertices
> > > call.
> > >
> > > I'm not sure when
On Wed, 2009-09-23 at 01:41 -0700, Dave Airlie wrote:
> >
> > Hey all,
> >
> > So in mesa for swtcl cases we emit vertices to DMA, and set a driver
> > internal dma.flush hook, we also set
> > ctx->Driver.NeedFlush |= FLUSH_STORED_VERTICES;
> >
> > The driver has its FlushVertices pointed at the
>
> Hey all,
>
> So in mesa for swtcl cases we emit vertices to DMA, and set a driver
> internal dma.flush hook, we also set
> ctx->Driver.NeedFlush |= FLUSH_STORED_VERTICES;
>
> The driver has its FlushVertices pointed at the vbo_exec_FlushVertices
> call.
>
> I'm not sure when this ever worke
Hey all,
So in mesa for swtcl cases we emit vertices to DMA, and set a driver
internal dma.flush hook, we also set
ctx->Driver.NeedFlush |= FLUSH_STORED_VERTICES;
The driver has its FlushVertices pointed at the vbo_exec_FlushVertices
call.
I'm not sure when this ever worked but I assume it did