On Wed, 2010-08-25 at 09:51 +0200, Sven Neumann wrote:
> I've done an update from DirectFB 1.4.3 to 1.4.5 with the result that a
> keyboard input device that used to be present before this update is now
> not any longer available.
>
> Now I wonder what happened to the "gpio-keys" device. I've checked that
> it is still present at /dev/input/event3. Why would DirectFB 1.4.5
> decide to ignore it?
I think I've found the answer. The following commit seems to be
responsible:
commit bc671612cb7b67c64deffab70763e17a8e721b63
Author: Ville Syrjala <syrj...@sci.fi>
Date: Thu Aug 20 11:53:49 2009 +0300
linux_input: Ignore devices w/o caps
Devices without caps are useless. Ignoring them will make it
less likely that MAX_LINUX_INPUT_DEVICES is exceeded and some
actually important input device gets left out.
The input device in question only has three keys. It is however not at
all useless. So I see two ways to fix this. Either back out this commit
or change the code in the linux_input driver to set the DICAPS_KEYS
capability for all devices that the EV_KEY bit set. I will send a patch
that does the latter. I've tested it and it fixes the problem for me.
Greetings,
Sven
--
Sven Neumann
Head of Software Development
RAUMFELD GmbH | Reichenberger Str. 124 | 10999 Berlin | Germany
Tel: +49.30.340.60.98.0 | Fax: +49.30.340.60.98.99 | s.neum...@raumfeld.com
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
