On Thu, 15 Mar 2007 16:38:05 -0400, Adam Jackson wrote: > There's just no making software texture interpolation fast enough.
It didn't sound like the use case being profiled here needed arbitrary transformations, (or even bilinear filtering). It sounded to me like just integer scaling, (which, as you touched on later, should allow us plenty of ways to cheat). And yes, the code should be asking for nearest neighbor filtering if that's all it needs. > That Render includes transforms and filters is very nearly academia > levels of solipsism. You just can't make them go fast in software, and > we already had a working API for doing them in hardware. Using Render > for untransformed alpha blending is at least reasonable to do in > software; Render ought to have stopped there. I think getting worked up about the Render interface isn't worthwhile. No applications that I'm aware of are coding directly to Render---none. The interface that is being used in applications is cairo, so all we have to do is make sure that cairo hits the right paths. And yes, cairo is currently calling into Render for transformations. Are you saying that cairo should be using something else instead and it will get better performance today? If so, I'm all ears. What should I be using instead to make cairo go faster? -Carl
pgpw3mMEpctnQ.pgp
Description: PGP signature
_______________________________________________ Devel mailing list [email protected] http://mailman.laptop.org/mailman/listinfo/devel
