Luis Mondesi wrote:
> I would like to explore with the solutions that you recommended here but I'm
> not sure how to proceed. Here is the questions that I have:
>
> Can we re-open the device without patching directfb?
Switching VTs back and forth would do this without a patch, but if you're using
the single application core (no --enable-multi) you can also just call this:
IDirectFB::Suspend()
and
IDirectFB::Resume()
But to avoid visual artifacts which I think would be there, the input driver
should be patched and reopen the device automatically.
> How can we avoid using a VT? I'm not too sure how the linux input driver is
DirectFBSetOption ("no-vt", NULL);
> supposed to work. I do know that there is a note about the linux_input
> driver causing problems on somebody's system (line 1126 of splashy_video.c
> http://git.debian.org/?p=splashy/splashy.git;f=src/splashy_video.c;hb=HEAD):
> /*
> * I disabled these modules, because they were causing problems on
> my
> * machine.
> */
> DirectFBSetOption ("disable-module", "linux_input");
That could be issues which are solved now, e.g. doubled events fixed by
grabbing the device.
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
