On Fri, 2005-11-04 at 14:02 +0000, Mark Adams wrote:
> I may be able to send you some very rough code to test this but I'd
> like you to do a test for me first:
>
> Remove the Flip() call entirely from your code and instead print out
> the current time (down to milliseconds, e.g. using gettimeofday).
> This will confirm what the up-stream code is trying to display.
OK: this is what I've done in video-dfb.c (for Stefan's benefit):
(ca. line 1295)
//videoSurface->Flip();
struct timeval tv;
gettimeofday(&tv,NULL);
fprintf(stderr, "Flip time: %i\n", (int) tv.tv_usec);
Now here is what I get in the output with DLOP_FIELD_PARITY enabled:
[dfb] (re)configuring Videolayer to 704 x 576 (704x576)
[dfb] SetParams: Enabling DLOP_FIELD_PARITY
[dfb]: SetParms (): trying to set DLBM_TRIPLE
[surface capabilities] videoSurface: videoonly flipping triple-buffered
[dfb] (re)configured 0x08100609
Flip time: 202386
Flip time: 279219
Flip time: 306769
Flip time: 357225
Flip time: 416181
Flip time: 447652
Flip time: 500761
Flip time: 531014
Flip time: 564100
Flip time: 604077
Flip time: 634689
Flip time: 663447
This works out (looking at other vales in the output) at between 28 and
59 ms or about 17 to 36 Hz! Should it be varying this much?!
If I turn off the DLOP_FIELD_PARITY stuff, the times work out between
about 33 and 55 ms (ca. 18 - 33 Hz).
I'm not sure whether this output is any use or not.
:-s
Cheers,
Laz
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
