<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - r200 falls back to software when clearing FBOs" href="https://bugs.freedesktop.org/show_bug.cgi?id=40554#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - r200 falls back to software when clearing FBOs" href="https://bugs.freedesktop.org/show_bug.cgi?id=40554">bug 40554</a> from <a class="email" href="mailto:sroland@vmware.com" title="Roland Scheidegger <sroland@vmware.com>"> Roland Scheidegger</a> <pre>(In reply to <a href="show_bug.cgi?id=40554#c4">comment #4</a>) > Clearing by drawing geometry? Isn't that somewhat inefficient? Doesn't the > hardware have a nicer way to deal with this? There are two normal methods how you can do ordinary buffer clears on this hw. 1) With the 2d blitter. 2) With the 3d engine (by drawing a tri/quad). In practice, both should most likely have the same performance, as it should be limited by memory bandwidth. I believe in theory the 2d blitter might be faster for this class of hardware, but IIRC you also get problems with 3d engine caches etc. Also, if you use 2d blit, you need to clear color and depth buffer separately. For depth/stencil buffer, you could use fast z clears (in some cases - it is tricky, for instance can't clear depth and stencil individually and not with pixel granularity viewport), which just sets a bit per tile saying this block is cleared. All hyperz functionality (which fast z clear is) is however defunct since dri2 (dri1 had it working mostly, was never enabled by default). > > It's now also applying ATI_fragment_shader shaders when clearing. I'll send > a patch for that. Hmm yes that sounds wrong.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>