>> Just upgraded to vanilla 2.6.33 + tp_smapi, from vanilla 2.6.32 + >> tp_smapi, and I've noticed a change in behavior of the Fn+F5 hotkey >> combination. > > Set Fn+F5 to KEY_BLUETOOTH in the thinkpad-acpi input device keymap. It > defaults to KEY_WLAN (will switch to KEY_RFKILL when that becomes > available). This is not what you want. udev can change that keymap, and so > can HAL and input-device userspace utilities. Changed it to KEY_BLUETOOTH just to test how it behaves. I've found that both udev and HAL would change the keymap (on ArchLinux) - so that path seems futile. Anyway, I've changed everything to bluetooth* and the funny thing is, now the bluetooth rfkill state gets blocked/unblocked by Fn+F5 with no daemons running - this again testing in single user mode with even udevd killed (only init and minilogd running). This is not the behaviour I like - where's my control? * and confirmed with "showkey" in a console that Fn + F5 emits a 237 keycode - and from the kernel source (include/linux/input.h 237 is KEY_BLUETOOTH) -- damjan ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
