problems with keymap entries in FDI-files

[Danny Kukawka]

Hi,

while sort and cleanup keymap entries for the new *_outof directives if found 
some 'unclear/obscure' issues:

* There are several cases where two scancodes get mapped to the same key or 
inversely one scancode mapped to two keys. While may the first case isn't 
that problematic, but may not what we want (e.g. in the acer file: 
e071:f22/e072:f22), I would say the second case is complete faulty (e.g. in 
the dell file: e008:wlan/e008:bluetooth) and useless. 
IMO we should at least remove the cases where the same scancode get mapped to 
two different keys.

* If I understand the How-To at [1] correct HAL should only contain mappings 
for 'unknown scancodes' (... You only need to remap keys using HAL that do 
not product valid keycodes (i.e. you get the warning in dmesg) as the others 
can be done with a keymap ...). 
But if I take a look at several mappings e.g. for the 'HP nc6320', some 
IBM/Lenovo or Acer laptops I wonder if all the mappings are really needed, 
because e.g. for the HP or a Lenovo T60 I couldn't reproduce the scancodes 
(also not if I boot to init=/bin/bash or with e.g. Kubuntu instead of SUSE). 
Do I miss or oversee something?

Comments?

Danny

[1] http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-index.html