On Tue, Mar 01, 2005 at 12:55:39PM +0100, Claudio Ciccani wrote:
Denis Oliver Kropp wrote:
Quoting Claudio Ciccani:
Teorically it should be support, but I haven't discovered how to make it work yet.
Would be great, because the conversion from non-tiled to tiled wouldn't be necessary anymore. Simply have ALL surfaces tiled.
TextureMapping on swizzled (texture) surfaces is supported, therefore at least NV4/NV5/NV10 could support that feature. Intead of adding new methods to IDirectFBSurface, I was thinking that Read()/Write() could be implemented as driver methods called from dfb_surface_hardware_lock()/dfb_surface_unlock(). What do you think about it?
In similar lines I was thinking about a new flag to Lock() that would indicate whether to (un)tile or not. But that would mean that we may have to tile and/or untile the whole surface for each Lock()/Unlock(). Read()/Write would allow partial updates and as such would be more efficient.
I suggested to use Lock()/Unlock() because that methods already exist and that way there is no need to specify that the surface is
tiled/non-tiled since the driver controls directly all read/write
accesses to video memory.
Read()/Write should be faster for the reason you said, but they could
be implemeneted only as replacement of Lock()/Unlock() to avoid
problems with texture format (specially with the Software Rasterizer).
-- Regards, Claudio Ciccani
[EMAIL PROTECTED] http://directfb.org http://sf.net/projects/php-directfb
_______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
