mirror of
https://github.com/Jeffrey-Sardina/liberated-systemd.git
synced 2026-10-18 17:20:51 -05:00
Sergey Tiraspolsky
0490b976b9
Like other pre-Vivaldi Chromebooks, the Pixelbook's top row sends the standard F1-F10 scancodes and Chrome OS translates them to actions in userspace, so elsewhere the keys come through as F1-F10 even though they are labelled Back, Refresh, Fullscreen, Overview, brightness down and up, play/pause, mute and volume down and up. Map them to the printed functions. Also map the menu key next to volume up (scancode 0x5d, F13 by default) to KEY_CONTROLPANEL and the Assistant key (scancode 0xd8, which atkbd reports as unknown) to KEY_ASSISTANT, as Chrome OS's own Eve hwdb does. XKB_FIXED_MODEL=chromebook, used for Falco and Peppy, does not fit: that model follows the original Chromebook top row (F2 Forward, F3 Refresh, brightness on F6/F7), while the Eve has Refresh on F2, brightness on F5/F6, Play/Pause on F7 and no Forward key. Tested on a Pixelbook with the DMI modalias dmi:bvncoreboot:bvrGoogle_Eve.9584.230.0:...:svnGoogle:pnEve:...
Files in this directory specify a description of hardware devices, in the form of mappings from modalias-like keys (which identify specific hardware devices) to udev properties. Files in this directory are not read by udev directly. Instead, man:systemd-hwdb(8) compiles them into a binary database. See man:hwdb(7) for an overview of the configuration file format, and man:systemd-udevd.service(8) for a description of the udev daemon. Use 'systemd-analyze cat-config udev/hwdb.d' to display the effective config.