| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fourteen years ago, commit b69a8bdff0 added a rule for redefining the
<NMLK> key for IBM Spacesaver keyboards in order to have `Num_Lock` on
both levels. This was needed to overwrite `Pointer_EnableKeys` that
was on the second level by default, which interfered with how the
Spacesaver NumLock key worked (https://bugs.freedesktop.org/16767).
Two years later, commit 1bc01a5eaa removed the default assignment of
`Pointer_EnableKeys` to the second level of <NMLK>, thus making the
special rule for IBM Spacesavers redundant.
(There are still a few vendor files that assign `Pointer_EnableKeys`.
These assignments should probably be removed too.)
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Having them in symbols/pc instead of in symbols/inet(evdev) means that
any assignments that a custom layout makes to these keys will not get
overridden by the standard +inet(evdev) rule.
This fixes issue #50.
Reported-by: Alex-Daniel Jakimenko
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
|
| |
|
|
|
|
|
|
|
|
| |
This adds a model for the Pine64 PinePhone Keyboard
(https://wiki.pine64.org/wiki/PinePhone_(Pro)_Keyboard).
Specifically, it implements the symbols listed on the top
row of the keyboard as a third layer which are not
available in the kernel driver.
|
|
|
|
| |
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
|
|
|
|
| |
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
| |
Fix typos (mainly capitalization) to improve consistency in naming of layouts
|
|
|
|
|
|
|
|
| |
These were added as comments only, presumably to reserve the key for future
updates. They are now mapped as part of the autogenerated keysym range and we
can remove these comments.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
|
|
|
|
|
| |
These symbols were added manually but are now autogenerate from the protocol
headers. To simplify the symbols table, drop the manually added ones and let
them be autogenerated - this way we need less duplicate detection and the
symbols themselves are in-order with the rest.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
xorgproto 2021.2 and later has a recognizable pattern for adding new keysyms
to XF86keysym.h based on the Linux kernel input-event-codes.h. Use this to
detect any keysyms that are present in the header file but not yet in
symbols/inet.
This is merely a gitlab CI job as we only have to do an actual update once
every few months or so. A git diff is sufficient here too, it contains all the
information we will need to understand what is missing from the updated file.
We check xorgproto master because that gives us some heads-up on what will
come. There is a minor chance that we are mapping keycodes that change before
the release but it's minor and fixable anyway.
Requires: https://gitlab.freedesktop.org/xorg/proto/xorgproto/-/merge_requests/23
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
OUTP has been mapped to XF86Display in symbols/pc for about 13 years now, but
no evdev keycode is mapped to this alias. Instead, we have I235 mapped to
XF86Display in symbols/inet. Alias I235 to OUTP and remove the separate
mapping, the keymap stays the same.
Fixes xkbcomp warning
Warning: Key <OUTP> not found in evdev+aliases(qwerty) keycodes
Symbols ignored
The same goes for KITG/KIDN/KIUP, all of which are mapped in symbols/pc.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The keyboard of the Acer TravelMate 5735Z has dedicated currency keys
close to the arrow keys. Currently, these are not working.
`libinput debug-events` reports the events below.
event0 KEYBOARD_KEY +7.161s KEY_EURO (435) pressed
event0 KEYBOARD_KEY +7.305s KEY_EURO (435) released
event0 KEYBOARD_KEY +7.708s KEY_DOLLAR (434) pressed
event0 KEYBOARD_KEY +7.852s KEY_DOLLAR (434) released
So, add the corresponding mappings. With these changes, pressing these
keys results in € and $ being displayed by GNOME Shell 3.36.3.
Closes: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/213
|
|
|
|
| |
Fixes: commit 28bb029b ("Map evdev keycode KEY_FULL_SCREEN to XF86XFullScreen")
|
|
|
|
| |
Too old to be supported
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Add layout for Microsoft Surface bluetooth keyboard.
Signed-off-by: Casey Strouse <casey.strouse@gmail.com>
|
|/
|
|
|
|
|
|
|
| |
Add XF86XFullScreen, to be used as mapping for evdev's KEY_FULL_SCREEN.
The patch for adding the FullScreen keysym to xproto is here:
https://gitlab.freedesktop.org/xorg/proto/xorgproto/merge_requests/11
Signed-off-by: Sebastian Wick <sebastian@sebastianwick.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add XF86RotationLockToggle, to be used as mapping for evdev's
KEY_ROTATE_LOCK_TOGGLE.
I've a Point of View P1006W-232 Windows tablet which actually has a
rotate-lock toggle-button. The latest kernel correctly generates
KEY_ROTATE_LOCK_TOGGLE events for this. So now I'm hooking up support for
it through all the higher layers.
The patch for adding the RotationLockToggle keysym to xproto is here:
https://patchwork.freedesktop.org/patch/279365/
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
| |
KEY_SOUND is used on actual devices and recent xproto versions
defines the AudioPreset keysym for this key.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
KEY_KEYBOARD has an evdev-keycode value of 374 not 366. It seems that
with the original addition of the mapping the evdev-keycode value was
mistaken for the X scancode which is 8 higher then the evdev-keycode
since the X scancodes start at 8. What seems to have happened is that
the evdev-keycode was used instead of the X scancode and then 8 was
subtracted for the wrong "// #define KEY_KEYBOARD 366" comment.
This commit corrects the comment to say 374 and corrects the X
scancode being mapped to 382.
Cc: Christian Kellner <christian@kellner.me>
Reviewed-by: Christian Kellner <christian@kellner.me>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
| |
|
|
|
|
| |
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/67
|
|
|
|
|
|
|
|
|
|
| |
Add XF86MonBrightnessCycle keybinding, to be used as mapping for evdev's
KEY_BRIGHTNESS_CYCLE keycode which is generated from ACPI video module's
ACPI_VIDEO_NOTIFY_CYCLE_BRIGHTNESS on some Acer AIO desktop buttons.
The button changes the screen's brightness on Windows.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=108861
Signed-off-by: Jian-Hong Pan <jian-hong@endlessm.com>
|
|
|
|
|
|
|
|
|
|
| |
NB: XF86Keyboard is a relatively new keysym and therefore needs
recent protocol headers. Also KEY_KEYBOARD's keysym is > 255
and therefore needs a recent xkbcomp (as the new KEY_FAVORITES).
https://bugs.freedesktop.org/show_bug.cgi?id=101521
Signed-off-by: Christian Kellner <christian@kellner.me>
|
|
|
|
|
|
|
|
|
|
|
| |
NB: The value of KEY_FAVORITES is 0x16c (364) and thus beyond 255,
which is not supported by X11. It might also need a recent xkbcomp
that is patched so it does not throw fatal errors for those. See
https://lists.x.org/archives/xorg-devel/2017-April/053389.html
https://bugs.freedesktop.org/show_bug.cgi?id=100709
Signed-off-by: Christian Kellner <christian@kellner.me>
|
|
|
|
|
|
|
| |
In particular KEY_RFKILL is required for properly handling airplane mode
in userspace.
https://bugs.freedesktop.org/show_bug.cgi?id=100970
|
| |
|
|
|
|
|
| |
Otherwise the file is not well fromed and xkbcomp (at least version
1.3.0) will refuse to compile it.
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=90960
|
|
|
|
|
|
|
|
|
| |
The recent Chromebooks have a different layout than general laptops.
Their F1-F10 keys are represented as generic function keys (brightness
up/down, etc...), and they lack a caps lock, delete, home, end, page up
and page down key.
Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
|
|
|
|
| |
Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=79219
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The keyboard driver (for legacy keyboards) reports the same
keycodes for some inet keys as for the extra keys (Henkan and
Muhenkan) on Japanese 106 keyboards.
So on these keyboards Japanese users either loose their extra
keys or some multimedia keys.
In:
commit bd9d0ced6154de583c96573585f428618017fca3
Fix henkan key on jp106 keyboard with inet media keys
the Henkan/Muhenkan keys were reintroduced.
A better fix will map one of the two sets to different and still
unused keycodes.
A patch for the xf86-input-keyboard driver moves the two inet keys
into the range above 0xfb.
This patch contains the corresponding changes to xkeyboard-config.
Both the legacy keyboard driver and xkeyboard-config will have to
be updated simultaniously otherwise users will loose the two affected
multmedia keys.
Signed-off-by: Egbert Eich <eich@freedesktop.org>
|
|
|
|
|
|
|
| |
Also adding some blank lines for consistency, unfolding some lines,
and tweaking a few comments and removing useless ones.
Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
|
|
|
|
| |
Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From checking the usage of KEY_CYCLEWINDOWS in the linux sources, it
seems to be meant for task switching, rather than rotating the screen
as XF86RotateWindows traditionally does. In turn, KEY_DIRECTION is what
some kernel platform modules already use for the "rotate display" key
in certain tablet models.
So in order to make things consistent, it makes more sense to map
KEY_DIRECTION to XF86RotateWindows, and KEY_CYCLEWINDOWS to XF86TaskPane
as it's the closest offered behavior.
Signed-off-by: Carlos Garnacho <carlosg@gnome.org>
|
|
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=54171
Signed-off-by: James M Leddy <jm.leddy@gmail.com>
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=59878
|
|
|
|
|
|
|
|
|
| |
According to symbols/inet this keycode is used by two keyboard models:
logitech_g15 and apple.
Thus it should not be used for a fake keycode that gets assigned to a
virtual modifier.
Signed-off-by: Egbert Eich <eich@freedesktop.org>
|
| |
|
|
|
|
| |
Ugh, sorry.
|
|
|
|
|
|
| |
Notably absent are any and all changes to the .po files as there _has_
to be a way not to do them by hand... Unfortunately, I was unable to
find it.
|
|
|
|
|
|
| |
Notably absent are any and all changes to the .po files as there _has_
to be a way not to do them by hand... Unfortunately, I was unable to
find it.
|
|
|
|
| |
Signed-off-by: Alexandr Shadchin <Alexandr.Shadchin@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apple's Expose and Dashboard keys (F3 and F4) have correct keycodes
reported by evdev, but are not mapped. This adds the required keycodes
and symbols, using the symbols XF86LaunchA and XF86LaunchB, which allows
the keys to be used in compiz configuration.
(This patch has been included in Ubuntu since 2010.)
Bug: #34351
Ref.: https://bugs.launchpad.net/ubuntu/+bug/520519
Signed-off-by: Bryce Harrington <bryce@canonical.com>
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=32653
|
|
|
|
|
|
|
|
| |
The IT and DE keyboard were mapped looking at real hardware that I have,
but the US one was done looking at:
http://upload.wikimedia.org/wikipedia/commons/1/18/T-Mobile_G1_launch_event_2.jpg
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=31333
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=5783
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=28972
|