good day! I'm developing an embedded system based on OMAP5912, linux 2.6.23 and DirectFB 1.1. the device has an keypad attached to the standard OMAP keypad port, and the kernel has the driver for it. during the application startup DIrectFB knows about it:
> (*) Direct/Thread: Running 'Linux Input' (INPUT, 3174)... > (*) DirectFB/Input: omap-keypad (1) 0.1 (directfb.org) (*) Direct/Thread: Running 'Linux Input' (INPUT, 3175)... (*) DirectFB/Input: Genius Optical Mouse (2) 0.1 (directfb.org) (*) Direct/Thread: Running 'Linux Input' (INPUT, 3176)... (*) DirectFB/Input: HID 0566:3002 (3) 0.1 (directfb.org) (*) Direct/Thread: Running 'Linux Input' (INPUT, 3177)... (*) DirectFB/Input: HID 0566:3002 (4) 0.1 (directfb.org) (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 3178)... (*) DirectFB/Input: Keyboard 0.9 (directfb.org) (*) Direct/Thread: Running 'PS/2 Input' (INPUT, 3179)... (*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org) 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. any suggestions? thanx. -- _____________ Oleg V. Kobrin _______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
