how can one identify bottlenecks in video card driver? i always thought it's nigh impossible.There are other bottleneck like some GL stuff which are not handled well enough currently (enemy territory use some of this). Anyway there is work underway to address most of pitfall of current open source driver. What is hard is that we need to keep backward compatibility so we endup doing crazy things just to make sure we do not break old things (new drm should work with new Xserver, new Xserver should work with old drm, new dri driver should work with old drm, ...).
is it mostly guesswork, or are there actual tools for the job?
now that i think about it, why do we need a whole truck to fill a glass? :>While the glass may not be full of water, there is a water truck on the away.
on the away...ohh, i get it now.on the away.
Last edited by yoshi314; 07-23-2007 at 09:31 AM.