Great! >Where do you think we could commit this bug to have a better >linux_input devices recognition in next versions? I don't know how to do it. I send a notification in mailing for these reasons. I hope that in the next release the problem will be fixed.
Giulio 2007/8/7, Mickael Istria <[EMAIL PROTECTED]>: > > Giulio Pollini wrote: > > Hi, > Hello > > I had a similar problem, please look my post of yesterday. > > I attached 2 example for test the input device. Compile them. Rememer to > > include the path of your kernel/Include. > > Could you send me the output of ex6.c. > > I see that the linux_input driver of DirectFB don't start the keyboard > input > > device if it doesn't recognize at least 20 keys beteewn KEY_Q ann KEY_M. > > > > I resolved my problem by change a line in linux_input.c (search KEY_Q). > > > > Giulio > > > > > > I did the same kind of modification (actually, I removed the condition > on number of keys to make linux_input guess it has to start keyboard > driver - I don't think it is better, but in this case it won't be a > problem) > > Here is the output of ex6 (thank you for this test program, it is very > useful!) > Supported Keys: > Key 0x02 (1) > Key 0x03 (2) > Key 0x04 (3) > Key 0x05 (4) > Key 0x06 (5) > Key 0x07 (6) > Key 0x08 (7) > Key 0x09 (8) > Key 0x0a () > Key 0x0b () > Key 0x1c (Enter) > Key 0x37 (*) > Key 0x3b (F1) > Key 0x3c (F2) > Key 0x3d (F3) > Key 0x40 (F6) > Key 0x67 (Up) > Key 0x69 (Left) > Key 0x6a (Right) > Key 0x6c (Down) > Key 0x6f (Delete) > > > df_input seems to work fine, I may just have to modify a little bit of > mapping. > > Where do you think we could commit this bug to have a better > linux_input devices recognition in next versions? > > Thank you very much! > > Mickael Istria > >
_______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
