On Tue, 27 Mar 2007 12:51:54 +0200 Denis Oliver Kropp <[EMAIL PROTECTED]> wrote:
> Denis Oliver Kropp schrieb: > > Tim Dijkstra schrieb: > >> Hi, > >> > >> A while back I've added splash support to the userspace software > >> suspend utility found at suspend.sf.net. Underneath it uses directfb. > >> There is one bit I haven't quite got to work and that is really simple > >> keyboard input. > >> > >> The problem is that during suspend, we instruct the kernel to freeze > >> all userspace except the thread we're currently in. If we do this it > >> seems we loose the keyboard too. Now my suspicion is that keyboard > >> support directfb always uses a different thread. > > > > Yes, DirectFB usually has an input thread per device. > > > > Do you get error messages? Maybe the read() result code needs some > > special handling in your case. No, no error it's DFB_OK > Now I see. Yes, you need to keep the keyboard thread alive as well > if you depend on it to resume. That is to bad. We can only have one thread during the freeze. If I could just read the keyboard state, without input buffer and the like, that would be enough for me. There is no loop hole for that? grts Tim
signature.asc
Description: PGP signature
_______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
