I note that evdev-1.1.2 had a 'workaround', so at least some of the keys
on these keyboards would work -- it would blindly remap the keycodes:
X keycode = ((kernel keycode + 8) mod 256)
It's nasty, but at least it allows users with strange devices (like my
Logitech UltraX) to work...
--
MAS
I note that evdev-1.1.2 had a 'workaround', so at least some of the keys
on these keyboards would work -- it would blindly remap the keycodes:
X keycode = ((kernel keycode + 8) mod 256)
It's nasty, but at least it allows users with strange devices (like my
Logitech UltraX) to work...
--
MAS
I note that evdev-1.1.2 had a 'workaround', so at least some of the keys
on these keyboards would work -- it would blindly remap the keycodes:
X keycode = ((kernel keycode + 8) mod 256)
It's nasty, but at least it allows users with strange devices (like my
Logitech UltraX) to work...
--
MAS
I note that evdev-1.1.2 had a 'workaround', so at least some of the keys
on these keyboards would work -- it would blindly remap the keycodes:
X keycode = ((kernel keycode + 8) mod 256)
It's nasty, but at least it allows users with strange devices (like my
Logitech UltraX) to work...
--
MAS
I note that evdev-1.1.2 had a 'workaround', so at least some of the keys
on these keyboards would work -- it would blindly remap the keycodes:
X keycode = ((kernel keycode + 8) mod 256)
It's nasty, but at least it allows users with strange devices (like my
Logitech UltraX) to work...
--
MAS
I note that evdev-1.1.2 had a 'workaround', so at least some of the keys
on these keyboards would work -- it would blindly remap the keycodes:
X keycode = ((kernel keycode + 8) mod 256)
It's nasty, but at least it allows users with strange devices (like my
Logitech UltraX) to work...
--
MAS