Thanks, for the answer, but, I don't have anything in /dev/input/ for
the moment.
My system looks like this :
ttyS0 is the system console
ttyS1 is the serial mouse
I have a shell running on /dev/ttyS0 and when I start a dfb application,
I would like to have the keyboard input form the console to the dfb app.
More precisely I would like to see the keyboard layer when I use dfbinfo
because GTK needs this keyboard layer to start any gtk application :
gtk+-2.10.13/gdk/directfb/gdkdisplay-directfb.c
ret=directfb->GetInputDevice (directfb, DIDID_KEYBOARD, &keyboard);
if (ret != DFB_OK){
DirectFBError ("gdk_display_open: GetDisplayLayer", ret);
return NULL;
}
I really don't know how the kernel input drivers are working, so the
question is :
Is it normal that I have nothing in /dev/input ? Specificaly no eventX
file that would correspond to my console input . ( Obviously the linux
input support and evdev are activated in my kernel, but maybe not
perfectly )
If it's normal , then I should write a uinput daemon that reads
/dev/console and write into /dev/uinput but it's not interresting for me
since it would be useless for the final application ( no keyboard, only
the touchscreen ).
Thanks,
Arnaud Derasse
Budulea Eduard a écrit :
> The controlling terminal should be ok for keyboard input.
> If it is not sufficient, it is trivial to make a daemon that reads from
> serial and writes keyboard event to a uinput dev file that it opens.
> The advantage of using a uinput is that the kernel will automatically
> converge all keyboard input to the keyboard driver.
> There is no reason to mess with gtk.
> For better reference look at:
> http://www.einfochips.com/download/dash_jan_tip.pdf
>
> _______________________________________________
> directfb-users mailing list
> [email protected]
> http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
>
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
