Oleg V. Kobrin wrote: > after the startup the input is redirected to the DirectFB event queue > and unavialable to the other applications and cannot be read from > /dev/input/event0. but, when I enumerate the input devices by the > EnumInputDevices() call, the omap-keypad device does not appear there: > > Input device 1, type 2, caps 6, keycodes ffffffff-ffffffff, name > 'Genius Optical Mouse', vendor 'Linux' > Input device 0, type 1, caps 1, keycodes 0-7f, name 'HID 0566:3002', > vendor 'Linux' > Input device 17, type 0, caps 4, keycodes ffffffff-ffffffff, name 'HID > 0566:3002', vendor 'Linux' > Input device 18, type 1, caps 1, keycodes 0-7f, name 'Keyboard', > vendor 'Unknown' > Input device 19, type 2, caps 6, keycodes ffffffff-ffffffff, name > 'IMPS/2 Mouse', vendor 'Unknown' > > and so no input events received into the buffer created by > CreateInputEventBuffer(dfb, DICAPS_KEYS, DFB_TRUE, &buffer) call.
I remember a similar issue. I think the reason was that none of the caps flags was set, but I'm not sure. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
