Arnaud Derasse wrote:
> 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 )
>
I think the first thing you should try is creating /dev/input/event0 and
/dev/input/event1 devices with mknod. event0 will most likely be
assigned to your mouse/touchscreen so you need event1 to pick up the
keyboard. Are you using udev or something similar so that you should
expect these devices to be automatically created?
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
