Ville Syrjälä wrote: > On Tue, Aug 07, 2007 at 09:57:31AM +0200, Mickael Istria wrote: >> Hello, >> >> I am trying to install DirectFB on an ARM phone using a recent Linux >> kernel (2.6.19 as far as I remember). >> I have a problem with input. >> >> Indeed, I activate linuxinput driver for my keypad (which uses >> /dev/input/event0 device), and I disable keyboard module. >> When I run any program using DirectFB, I have both following lines which >> make me hope that everything is right: >> >> (*) Direct/Thread: Running 'Linux Input' (INPUT, 215)... >> (*) DirectFB/Input: PNX5220 Keypad 0.1 (directfb.org) >> >> But dfbinfo returns me that he only see output for the display, and can >> not see any input (whereas there is this keypad). > > The problem is that linuxinput fails to classify the device. It's not > really a keyboard as far as linuxinput is concerned since it doesn't > have enough alphabetic keys, nor does it think it is a remote control. > I'm not sure which classification would be more appropriate, or maybe we > should add DIDTF_KEYPAD?. The most important issue is the missing > DICAPS_KEYS. Without some caps the device is never enumerated (it is > registered to the input core though and thus wastes some memory).
Another type is a good idea. I think a keyboard is something lets you type text or use a console. Keypads are subsets, e.g. numeric, or front panels with cursor keys and OK, probably Channel Up/Down, which could lead DirectFB to think of it as a remote, right? Anyhow, it should have DICAPS_KEYS at least, as you mentioned. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
