On Mon, 2005-05-23 at 18:45 +0200, Nicolai Haehnle wrote: > > It is equally likely that the lockup is caused by, say, alignment or > wraparound issues of the ring buffer. > Note that fglrx always submits commands in indirect buffers, which are > stored linearly in physical memory. We, on the other hand, always submit > commands into the ring buffer, which is not linear (because it wraps > around). Also, fglrx likes to emit NOPs into the command stream sometimes, > though I haven't been able to find an exact pattern in those NOPs. We never > emit NOPs (or do we?). > > So the fact is: We just don't know whether alignment/wraparound can cause > trouble. The emission of NOPs by fglrx is IMO significant evidence that > there *are* issues in this area, at least on some chipsets, but it could > just be some weird artifact of the fglrx codebase.
The NOPs in the ring buffer are there for alignment/performance reasons, they shouldn't affect lockups either way. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_idt02&alloc_id135&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
