Hi,
I am using a Beaglebone black with a HDMI monitor. As far as I see the beaglebone uses the tilcdc driver for framebuffer (I am using the linux-dev-3.13.6-bone7 kernel).
When I am correct this driver does not implement the FBIO_WAITFORVSYNC ioctl. Is there any other way to get the vsync in userspace or in a kernel module?
Sorry for my poor english and thanks for every answer - Robert
On Wed, Mar 12, 2014 at 5:40 AM, Robert Kuhn robert@ku.hn wrote:
Hi,
I am using a Beaglebone black with a HDMI monitor. As far as I see the beaglebone uses the tilcdc driver for framebuffer (I am using the linux-dev-3.13.6-bone7 kernel).
When I am correct this driver does not implement the FBIO_WAITFORVSYNC ioctl. Is there any other way to get the vsync in userspace or in a kernel module?
you probably should use the KMS interface directly, rather than fbdev. Then you can modeset, do actual pageflips, get vblank events, etc.
A couple examples:
modetest - test code which does not use gpu and demonstrates most of the kms features http://cgit.freedesktop.org/mesa/drm/tree/tests/modetest
kmscube - simple example showing integration of gpu and kms https://github.com/robclark/kmscube
BR, -R
Sorry for my poor english and thanks for every answer - Robert
dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi,
Rob Clark [robdclark@gmail.com]:
you probably should use the KMS interface directly, rather than fbdev. Then you can modeset, do actual pageflips, get vblank events, etc.
A couple examples:
Thanks for the hint. I compiled modeset buth was overwhelmed with the mode string (-s parameter).
Now I got a working example from https://raw.github.com/dvdhrm/docs/master/drm-howto/modeset.c and it seems it does what I want.
Thanks!
I know this is a developer list but I hope its okay to ask such questions.
dri-devel@lists.freedesktop.org
-
Rob Clark -
Robert Kuhn