Page MenuHomeFreeBSD

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

Authored by val_packett.cool on Sep 8 2019, 2:59 PM.
Tags
Referenced Files
Unknown Object (File)
Fri, Jul 5, 1:20 AM
Unknown Object (File)
Sun, Jun 30, 11:30 PM
Unknown Object (File)
Sat, Jun 29, 12:37 AM
Unknown Object (File)
Thu, Jun 20, 6:30 AM
Unknown Object (File)
May 31 2024, 12:34 PM
Unknown Object (File)
May 13 2024, 8:30 AM
Unknown Object (File)
May 10 2024, 3:57 PM
Unknown Object (File)
Apr 19 2024, 1:42 PM
Subscribers

Details

Reviewers
wulf
Group Reviewers
Contributor Reviews (src)
Summary

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

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
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 https://www.win.tue.nl/~aeb/linux/kbd/scancodes-6.html, 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