I found that the following keys on the Samsung have scan codes but are not configured:
Fn+UP = 0x88 (e008)
Fn+Down = 0x89 (e009)
Fn+F2 = 0x83 (e003)
Fn+F4 = 0x82 (e002)
Fn+F5 = 0x84 (e004)
Fn+F7 = 0xb1 (e031)
Fn+F8 = 0xb3 (e033)
Fn+F9 = 0x86 (e006)
This is also noted in the following launchpad bug report: bugs.launchpad.net/ubuntu/+source/linux/+bug/399911?comments=all
So, it appears as if the key_release patch is indeed in the kernel, which means the next step should be to assign the above scan codes to actual keys and functions (such as adjust brightness etc).
Честно скомунижжено оттуда ubuntuforums.org/archive/index.php/t-1313956.html
After installing the 2.6.32 kernal and following the very informative instructions detailed here: wiki.archlinux.org/index.php/Extra_Keyboard_Keys
I found that the following keys on the Samsung have scan codes but are not configured:
Fn+UP = 0x88 (e008)
Fn+Down = 0x89 (e009)
Fn+F2 = 0x83 (e003)
Fn+F4 = 0x82 (e002)
Fn+F5 = 0x84 (e004)
Fn+F7 = 0xb1 (e031)
Fn+F8 = 0xb3 (e033)
Fn+F9 = 0x86 (e006)
This is also noted in the following launchpad bug report: bugs.launchpad.net/ubuntu/+source/linux/+bug/399911?comments=all
So, it appears as if the key_release patch is indeed in the kernel, which means the next step should be to assign the above scan codes to actual keys and functions (such as adjust brightness etc).
Честно скомунижжено оттуда ubuntuforums.org/archive/index.php/t-1313956.html