Re: Bug: changing keycodes generated by sony-laptop doesn't work

[John Hughes]

On 10/16/2011 02:30 PM, John Hughes wrote:
> Something about the way sony-laptop sends scancodes and keycodes to 
> the input subsystem doesn't work.

I forgot to say that this is in 2.6.32.

Further testing shows that it is possible to change the keycode 
generated for a particular scancode but that the mapping is wrong.

For example:

# /lib/udev/keymap -i input/event6
Press ESC to finish
scan code: 0x00   key code: fn_e
scan code: 0x1B   key code: fn_e
^C
# /lib/udev/keymap  input/event6 0x14 ejectcd
setting scancode 0x14 to key code 161
# /lib/udev/keymap -i input/event6
Press ESC to finish
scan code: 0x00   key code: ejectcd
scan code: 0x1B   key code: ejectcd
scan code: 0x1B   key code: ejectcd
scan code: 0x1B   key code: ejectcd
^C

All the scancodes are 7 off, setting the mapping for scancode 0x14 
changes the mapping for what the driver claims is scancode 0x1B.

I guess this has something to do with a confusion between the jog-dial 
scancodes and the Vaio keys scancodes.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/