My keypad (on ARM target) have this keys:
 This keyboard have a 8x8 matrix with this supported key:

Supported Keys:
  Key  0x00  (Reserved)
  Key  0x01  (Escape)
  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  (9)
  Key  0x0b  (0)
  Key  0x0e  (Backspace)
  Key  0x0f  (Tab)
  Key  0x1c  (Enter)
  Key  0x1d  (LH Control)
  Key  0x2a  (LH Shift)
  Key  0x38  (LH Alt)
  Key  0x39  (Space)
  Key  0x3b  (F1)
  Key  0x3c  (F2)
  Key  0x3d  (F3)
  Key  0x3e  (F4)
  Key  0x3f  (F5)
  Key  0x40  (F6)
  Key  0x41  (F7)
  Key  0x42  (F8)
  Key  0x43  (F9)
  Key  0x67  (Up)
  Key  0x69  (Left)
  Key  0x6a  (Right)
  Key  0x6c  (Down)
  Key  0x8b  (Menu)

Giulio

2007/8/7, Denis Oliver Kropp <[EMAIL PROTECTED]>:
>
> 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
>
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

Reply via email to