On Thu, 2003-12-04 at 11:48, Mike A. Harris wrote: > > THe first step to me, would be to oprofile things, and find where > the bottleneck is, then try to determine why.
Good idea, but beware that the gprof output was rather confusing when I first saw this problem, the time would appear to be spent in random 3D driver functions when in fact it seemed to be waiting for the hardware most of the time. oprofile may do a better job there, but you've been warned. > If there are specific registers you don't understand and think > might be a problem, or any other code construct, feel free to > ask, and also to stick around in #dri-devel. While nobody can > provide you the docs except ATI, we can probably clarify some > uestions you might have about radeon hardware operation et al. > > IMHO, it's best to approach this from a direct concrete angle of > a specific problem though, rather than a general problem of PCI > not working properly and wanting to go over every inch of the > driver anc compare register usage to the manual. The latter IMHO > is a huge waste of time. Amen. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Software libre enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
