http://bugs.freedesktop.org/show_bug.cgi?id=18397
--- Comment #43 from Øyvind Stegard <[email protected]> 2009-02-10 14:26:09 PST --- (In reply to comment #41) > (In reply to comment #39) > > Now you're on the right direction. My infamous checkbox-test in > > Firefox/GMail > > shows there is improvement (it's better than I've ever seen it before with > > EXA). There are still rendering errors in a few check-boxes, but they are > > fewer > > now. I see idle-looping going on, should I try to increase the number of > > iterations before giving up and returning in RADEONWaitforIdlePoll() ? Or > > perhaps that does not make sense and is unwise .. Obviously racy little > > slime > > bug this. I noticed you put back the drm busy waiting code in the latest > > patch > > (in the DFS func), that at least seemed to help. Also, I see the only XXX: > > in > > radeon_exa_funcs.c is located above that part :). > > > > I think it's just adding latency. We really need to wait on a timestamp > written by the CP after rendering is done to be sure the hw is done and caches > are flushed. > Like you commented in the code. I wont pretend to know much at all about graphics drivers, but the CP facilitates a command queue/buffer(of register updates?) with GPU as consumer and CPU/driver-software as producer ? Just curious, really .. I'm a programmer by profession, but know very little about graphics drivers. It's interesting to look at, but still looks hellishly complex :) -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
