I am using mesa-solo in an application that attempts to generate simple 3d scenes at the full frame rate of the video card. I use an /etc/drirc file with the following option for my app:
<option name="vblank_mode" value="3"/>
this option is supposed to synchronize the swap to the VBLANK period. Based on my reading of the code, and based on actual measurements this works as advertised, and quite well.
I want to KNOW FOR CERTAIN that the swap occurred for a given frame, and that it didn't skip a frame or two in the process. When that happens, I need to know how many frames were missed. In some instances we use /dev/rtc for an independent measurement, but we cannot always rely on that solution.
Under ordinary X, there is GLX_OML_sync_control, which provides methods to determine whether frame(s) were missed.
The work for the above is all done in the r200_dri.so and the drm driver, ie the code which is (more or less) shared with mesa-solo.
Probably everything is in place for this extension, you just need to hook it up and enable it in Mesa-solo.
Keith
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
