On Friday 18 February 2005 18:17, Keith Whitwell wrote:
> Ben Skeggs wrote:
> > I'm still rather new at this, so forgive me if this is a bad suggestion.
> > How about going with option 2, but only submitting the command buffer
> > anyway if nr_released_bufs != 0.
> > 
> > Would this cause any unwanted side effects?  It seems better than just
> > always submitting buffers with no cliprects anyhow.
> 
> Oh, btw - note that if you start thowing buffers out, you have to 
> account for the fact that the hardware hasn't been programmed with the 
> state that you thought it had - probably by setting a dirty flag or lost 
> context flag.

The command buffer is always sent to the kernel now (and clipping is used to 
prevent any real rendering from happening), so this particular bug should 
be gone.

There's still at least one hardware lockup bug that can be triggered with 
glxgears; unfortunately, this one doesn't seem to be so easily 
reproducible.

cu,
Nicolai

> Keith

Attachment: pgpCHhXvCXfaI.pgp
Description: PGP signature

Reply via email to