Evdev drops all keyboard events with code > 255?
daniel at fooishbar.org
Thu Dec 4 00:13:47 PST 2008
On Thu, Dec 04, 2008 at 08:31:27AM +0100, Mattias Nissler wrote:
> I just got my new USB DVB-T dongle, which features an IR receiver and
> comes with a remote. It sort of works, but I have the following problem:
> My X server is configured to use evdev for all its input. This is fine
> also for the remote, since the kernel generates key input events for all
> buttons I can press on the remote (checked that with the input-events
> utility). However, xorg's evdev input driver currently drops all
> keyboard events with code < 255 (I've checked input-evdev-2.0.7, which
> I'm running, but the code seems to be the same for the current master
> branch). Thus, the buttons that happen to generate linux input keys with
> code > 255 do not show up in the X server, since input-evdev discards
> them (at least it prints a message in the log when doing so).
> Question is why this is the case and what can be done to overcome this
> situation. Anyone have patches/workarounds for this problem or an idea
> how to solve this?
It will be solved with Xi 2 or 3, but that will still require all
clients to upgrade before we can actually deliver any events; currently,
the X protocol limits us to 255 keycodes.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: Digital signature
More information about the xorg