[Dri-devel] Re: NO_BATCH_DISPATCH path

2002-06-05 Thread Leif Delgass
On Wed, 5 Jun 2002, José Fonseca wrote: > On 2002.06.05 20:34 Leif Delgass wrote: > > On Wed, 5 Jun 2002, José Fonseca wrote: > > > ... > > > > > > In _wait_ring you don't check if card is idle (and resume) so you could > > > be forever waiting for free space space. > > > > I do see the problem

[Dri-devel] Re: NO_BATCH_DISPATCH path

2002-06-05 Thread José Fonseca
On 2002.06.05 20:34 Leif Delgass wrote: > On Wed, 5 Jun 2002, José Fonseca wrote: > > ... > > > > In _wait_ring you don't check if card is idle (and resume) so you could > > be forever waiting for free space space. > > I do see the problem there, I was thinking that this couldn't be > triggered >

[Dri-devel] Re: NO_BATCH_DISPATCH path

2002-06-05 Thread Leif Delgass
On Wed, 5 Jun 2002, José Fonseca wrote: > On Tue, 4 Jun 2002, Leif Delgass wrote: > > On Tue, 4 Jun 2002, Jose Fonseca wrote: > > > > > Leif, > > > > > > As I was restructuring part of the DMA submission code I realized that > > > there is a fault in the NO_BATCH_DISPATCH path. You don't guarant

[Dri-devel] Re: NO_BATCH_DISPATCH path

2002-06-05 Thread Leif Delgass
On Tue, 4 Jun 2002, José Fonseca wrote: > Leif, > > As I was restructuring part of the DMA submission code I realized that > there is a fault in the NO_BATCH_DISPATCH path. You don't guarantee > that the card doesn't stop at any momment because you've chosen not > check if a change in the las