URL: http://cgit.freedesktop.org/~csimpson/mesa/log/?h=gallium-blitter
So, with r600g right around the corner, I'd like to do something about this blitter/no blitter thing. This patch series contains one new getparam, PIPE_CAP_BLITTER, and a proposed ABI change to accompany it. surface_copy and surface_fill are proposed to have a way of indicating whether or not they successfully performed the fill/blit. It is up to the state tracker to determine whether or not to rely on these functions. Issues: - Should surface_copy and surface_fill return boolean instead of void? With this patchset, they'll return FALSE if they fail, and always return FALSE if PIPE_CAP_BLITTER isn't set. - Instead, should surface_copy and surface_fill simply be allowed to be NULL if PIPE_CAP_BLITTER is set? State tracker could continue to assume that, if present, surface_copy and surface_fill behave as expected and never fail. - Should clear be included with these two? I don't think any drivers are doing anything with clear except wiring it up to util_clear... Comments, etc. greatly appreciated. The sooner this gets untangled, the sooner we can get proper render paths into Mesa st. ~ C. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
