Luis Mondesi wrote: > Hello all, > > Thanks to the folks at RPath [0], we were able to understood and patch > a bug that was making Splashy impossible to use from initramfs on > Linux [1] (while using init and not upstart to start all user-space > applications). > > The problem happens when the TTY from which Splashy is started gets > modified while the application is running (again, refer to RPath's > detailed ticket). The modification of this special file causes the > keyboard event function on directfb [2], to go into an infinite loop, > taking more and more CPU power as the boot process goes along. > > Apparently the solution to this problem is to simply release some CPU > cycles on the keyboardEventThread. This is done by simple applying the > following patch: > > --- directfb-0.9.25.1.orig/inputdrivers/keyboard/keyboard.c > +++ directfb-0.9.25.1/inputdrivers/keyboard/keyboard.c > @@ -279,6 +279,8 @@ > > keyboard_set_lights( data, evt.locks ); > } > + if (readlen <= 0) > + usleep(2000); > } > > if (readlen <= 0 && errno != EINTR) > > (Note that this is the same fix for directfb 1.1.x)
I made the change in the driver. Would reopening the device help? What about not using VTs at all, but use the Linux Input driver? -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
