Saturday, 15 March 2014

qt5.3 - Qt 5.3.2: Screen tearing after running a Quick 2.0 app by eglfs on TI AM335x -



qt5.3 - Qt 5.3.2: Screen tearing after running a Quick 2.0 app by eglfs on TI AM335x -

we got screen tearing after 10 mins running qt5 clocks illustration eglfs. behavior before 10 mins looks good, after below warning message maintain showing up:

could not wait vsync.

we saw message because do:

export qt_qpa_eglfs_forcevsync=1

the qsurfaceformat info is:

created context format qsurfaceformat(version 2.0, options qflags(), depthbuffersize 24, redbuffersize -1, greenbuffersize -1, bluebuffersize -1, alphabuffersize -1, stencilbuffersize 8, samples -1, swapbehavior 2, swapinterval 1, profile 0) config: egl_buffer_size: 16 egl_alpha_size: 0 egl_blue_size: 5 egl_green_size: 6 egl_red_size: 5 egl_depth_size: 24 egl_stencil_size: 8 egl_config_caveat: 12344 egl_config_id: 8 egl_level: 0 egl_max_pbuffer_height: 2048 egl_max_pbuffer_pixels: 4194304 egl_max_pbuffer_width: 2048 egl_native_renderable: 0 egl_native_visual_id: 0 egl_native_visual_type: 0 egl_samples: 0 egl_sample_buffers: 0 egl_surface_type: 7 egl_transparent_type: 12344 egl_transparent_blue_value: 0 egl_transparent_green_value: 0 egl_transparent_red_value: 0 egl_bind_to_texture_rgb: 0 egl_bind_to_texture_rgba: 0 egl_min_swap_interval: 1 egl_max_swap_interval: 1

by checking qt's source code, know setting qt_qpa_eglfs_forcevsync 1 allow qt ioctl fbio_waitforvsync. ioctl returns success until 10 mins after running app.

does has hints or suggestion on how eliminate tearing?

i misunderstand meaning of "tearing". situation because framebuffer console blanking mentioned in this link.

the solution turn off blanking kernel bootargs "consoleblank=0".

qt qt5.3

No comments:

Post a Comment