Page MenuHomeFreeBSD

atkbd,evdev: Interpret Google Assistant key on Chromebooks as right meta

Authored by on Sep 8 2019, 2:59 PM.
Referenced Files
Mon, Dec 4, 10:52 AM
F72255693: D21565.diff
Mon, Dec 4, 10:38 AM
Unknown Object (File)
Wed, Nov 29, 5:44 PM
Unknown Object (File)
Oct 22 2023, 10:39 AM
Unknown Object (File)
Oct 3 2023, 7:37 PM
Unknown Object (File)
Sep 18 2023, 8:08 PM
Unknown Object (File)
Jul 13 2023, 9:48 PM
Unknown Object (File)
Jul 6 2023, 3:21 AM


Group Reviewers
Contributor Reviews (src)

The Google Pixelbook has an Assistant key where the Win key usually is. It sends the 0x58 scancode that we didn't interpret as anything at all.

The search key (capslock) is left meta already, so let's interpret this as right meta I guess.

Diff Detail

rS FreeBSD src repository - subversion
Lint Skipped
Tests Skipped

Event Timeline

I don't think that Assistant key should be mapped to KEY_RIGHTMETA for following reasons:

  1. It is not really a meta key as it does not affect other key meanings like Shift, Alt, Ctrl and Win keys do.
  2. According to, scancode of 0x58 prefixed with 0xE0 is emitted by pressing of Fn+F12 keys on Logitech and Microsoft keyboards so the best matching evdev event would be KEY_FN_F12.

IMO we can add all 12 KEY_FN_FX evdev events as e0 variation of the ordinary or FX keys