[oe] [patch commit request] kdrive xserver: support for key codes 128-255

Paul Sokolovsky pmiscml at gmail.com
Wed Jan 30 10:45:44 UTC 2008


Hello,

On Mon, 28 Jan 2008 19:19:04 +0100
Stanislav Brabec <utx at penguin.cz> wrote:

> Hallo.
> 
> Would be anybody with commit privileges to OE mtn so kind and review
> and commit attached fixes regarding keycodes 128-255 in kdrive
> xserver.
> 
> It is required for input devices generating these key codes (e. g.
> Sharp CE-RH2 on Zaurus Spitz/Akita).
> 
> This patch works perfectly for me for more than half year.
> 
> Patch is not device specific and should work for all input devices. It
> was reviewed by the Linux Extended MEDIUMRAW mode author.
> 
> Attached mtn patch fixes
> http://bugs.openembedded.org/show_bug.cgi?id=2637
> [Bug 2637] fixes to make Sharp CE-RH2 remote working in X
> 
> This bug remains for more than half year without any response.
> 
> This bug is also pending in upstream as
> http://bugs.freedesktop.org/show_bug.cgi?id=11545
> [Bug 11545] patch to support Linux Extended MEDIUMRAW keyboard mode

Can you please elaborate what the application of this patch would mean
for OE (besides fixing support for one specific obscure peripheral)? 

Based on this comment: "Note: Extended MEDIUMRAW mode and evdev mode
should provide the same keycodes" in
http://bugs.freedesktop.org/show_bug.cgi?id=11545 , I would think that
it would bring us interface-stable workaround until X.org and we fully
convert to evdev? Is that how you perceive it? Should we declare the
problem of 8-bit keycodes solved right now, and stop recommending
kernel developers to fit their keys into 7 bits? Is this patch suitable
for merging to stable branch?


Thanks,
Paul




More information about the Openembedded-devel mailing list