I see I see. Since all input devices I have are non-ir devices, switching on "linux-input-ir-only" actually helps me get rid of linuxinput driver. Then it let keyboard driver have the chance to handle the input events from the keypad correctly. I gonna need to check why linuxinput driver cannot handle the input events from my keypad correctly.
Thanks a lot for clarifying this! /Song On 5/23/08, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: > > Song Yuan wrote: > >> Hi, >> I use Gtk+/DFB in embedded Linux on the device. I build DFB with >> linuxinput and keyboard as its input driver modules. In "/dev" folder, >> I have "input/event0", "input/event1" and "input/event2" that >> corresponds to different input devices. >> >> However, DFB can recognize three devices, a keypad, GPIO sensors and >> "Keyboard 0.9" (I think the last one is abstract, from "keyboard" >> module). But when I use "df_input", it cannot detect any input events. >> >> In directfbrc options, I try to turn on "linux-input-ir-only", then >> DFB can only recognize "Keyboard 0.9" as its sole input device, and >> "df_input" can also detect all input events from my keypad. >> >> Does DFB think the other two devices are IR devices? >> > > linux-input-ir-only makes the driver ignore any non-ir devices. > > It seems that the linux-input driver does not translate/handle the keys > from your pad properly and they end up as nothing. > > Because the linux-input driver grabs all devices that it handles, the > keys no longer end up in the keyboard driver, which gets already translated > events in case the linux-input driver did not grab 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
