News: 0001567447

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Linux 6.17 Standardizes The Keycode For The "Performance Boost" Key

([Hardware] 3 Hours Ago Performance Key)


With the input subsystem updates for Linux 6.17 in addition to now [1]mapping ther F13 to F24 keys by default for PS/2 keyboards, the "performance boost" key beginning to be found on some laptops now has a standardized keycode. With standardizing that keycode, Linux desktop/user-space software will be able to more easily and uniformly set the intended behavior should your laptop/system have such a performance key.

Some relatively recent Dell/Alienware gaming laptops have [2]featured a G-Mode key aimed to help with gaming performance and other "performance boost" keys have appeared on other devices. These keys typically are just for switching the laptop over to the high performance platform profile rather than having to adjust your power/performance profile from within the operating system's settings interface.

With Linux 6.17, there is now a standardized keycode for such performance keys. Marcos Alano commented on [3]the patch defining KEY_PERFORMANCE as 0x2bd :

"Alienware calls this key "Performance Boost". Dell calls it "G-Mode".

The goal is to have a specific keycode to detect when this key is pressed, so userspace can act upon it and do what have to do, usually starting the power profile for performance."

That patch was [4]merged as part of the input driver updates today for Linux 6.17. The Linux 6.17 merge window is expected to culminate this weekend with the Linux 6.17-rc1 release.



[1] https://www.phoronix.com/news/Linux-6.17-Input-Drivers

[2] https://www.phoronix.com/news/Alienware-G-Mode-Linux-Revert

[3] https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/commit/?id=89c52146392948f4cdda3853da9d82ec6d1dd1f4

[4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6e64f4580381e32c06ee146ca807c555b8f73e24



M@GOid

OlafLostViking

Zqpvr01

Chugworth

Alex/AT

StarterX4

microcode

touchdown

fitzie

While the year 2000 (y2k) problem is not an issue for us, all Linux
implementations will impacted by the year 2038 (y2.038k) issue. The
Debian Project is committed to working with the industry on this issue
and we will have our full plans and strategy posted by the first quarter
of 2020.