[EMAIL PROTECTED] wrote: > New commits: > http://git.directfb.org/?p=core/DirectFB.git;a=commit;h=0d9188ce2911c3aba09f9c4a5ea174ef7f9d2b33 > commit 0d9188ce2911c3aba09f9c4a5ea174ef7f9d2b33 > Author: Ville Syrjala <[EMAIL PROTECTED]> > Date: Mon Aug 27 23:13:22 2007 +0300 > > Avoid unnecessary dfb_gfxcard_sync(). > > Avoid waiting for idle accelerator twice by clearing the GPU read > access flag when handling GPU write access. > > src/core/surface_buffer.c | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > http://git.directfb.org/?p=core/DirectFB.git;a=commit;h=22ac13e66da5409ff1b0b28bb6477aa144f9955d > commit 22ac13e66da5409ff1b0b28bb6477aa144f9955d > Author: Ville Syrjala <[EMAIL PROTECTED]> > Date: Mon Aug 27 23:10:45 2007 +0300 > > Fix CPU read/write access confusion. > > CPU read access after GPU read does not need any handling. CPU write after > a GPU read needs a sync. Flushing the texture cache is not needed. > > src/core/surface_buffer.c | 6 ++---- > 1 files changed, 2 insertions(+), 4 deletions(-) > > http://git.directfb.org/?p=core/DirectFB.git;a=commit;h=fd596f8f4c906d78ebbf1d710448aaef01cfb208 > commit fd596f8f4c906d78ebbf1d710448aaef01cfb208 > Author: Ville Syrjala <[EMAIL PROTECTED]> > Date: Mon Aug 27 23:06:42 2007 +0300 > > Flush the read cache only when a CPU read access is requested.
Thanks for all your fixes. In this case we always need to do the flush because next time the flag might not be set anymore and we don't flush at all. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-cvs mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-cvs
