- 11 Mar, 2021 1 commit
-
-
Pierre Le Marre authored
Fixes #20
-
- 10 Mar, 2021 6 commits
-
-
Peter Hutterer authored
Build and install with meson, build and install with autotools and then run diff to compare the two directory trees. They should be the same. This does not install the legacy protocols, they're behind a configure switch. The spec-build is disabled in autotools because we know meson doesn't do that yet, so no point in comparing those. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This now matches the autotools installation Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Generated outputs are identical Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
autotools can't pass arguments, so let's default to 'verify' in the script itself and for distcheck to succeed, we need to set an environment variable to search for the header (it's an out-of-tree build). And due to the very faint chance of there being no python during the xorgproto build, let's make that conditional too. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
More readable grouping this way Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
An alphabetically ordered list is nice, but it's harder to figure out based on a diff whether a commit affects the legacy protocols or not. Let's group those separately, first the normal protocol files, then all the legacy-only ones. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 01 Mar, 2021 1 commit
-
-
- 25 Feb, 2021 1 commit
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 24 Feb, 2021 5 commits
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 17 Feb, 2021 3 commits
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
No change to the header, comments only. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 08 Feb, 2021 20 commits
-
-
Peter Hutterer authored
These keysyms were already present in 2.6.11 which is the first tag in git. A few notes on specific keys here: - KEY_EJECTCLOSECD is theoretically different to XF86XK_Eject (kernel KEY_EJECTCD) but the actual usage in the hwdb remappings seems to be random. Either way it's already mapped to XF86XK_Eject in symbols/inet so let's just add an entry for the sake of documenting it. - XF86XK_CycleAngle seems like the best match for KEY_ANGLE Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
A few notes on specific keys here: - Some existing keysyms used some brand names. e.g. KEY_WORDPROCESSOR -> existing XF86XK_Word. This introduces some minor inconsistency with unbranded new keys like KEY_GRAPHICSEDITOR -> XF86XK_GraphicsEditor. - XF86XK_DisplayToggle is *not* XF86XK_Display (which represents KEY_SWITCHVIDEOMODE) Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
A few notes on specific keys here: - There are exiting XF86XK_ZoomIn/Out keys, but they don't seem appropriate for KEY_CAMERA_ZOOMIN and friends. New symbols are introduced here. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
ALSToggle has a terrible name, it's the Ambient Light Sensor. But it matches the kernel define so... Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This keysym is already available under a different name, see xorg/proto/xorgproto@000ebed5 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The Linux kernel adds a few evdev keycodes roughly every other release. These aren't available as keysyms through XKB until they have been added as keycode in xkeyboard-config and mapped there to a newly defined keysym in the X11 proto headers. In the past, this was done manually, a suitable keysym was picked at random and the mapping updated accordingly. This doesn't scale very well and, given we have a large reserved range for XF86 keysyms anyway, can be done easier. Let's reserve the range 0x10081XXX range for a 1:1 mapping of Linux kernel codes. That's 4095 values, the kernel currently uses only 767 anyway. The lower 3 bytes of keysyms within that range have to match the kernel value to make them easy to add and search for. Nothing in X must care about the actual keysym value anyway. Since we expect this to be parsed by other scripts for automatic updating, the format of those #defines is quite strict. Add a script to generate keycodes as well...
-
- 20 Jan, 2021 1 commit
-
-
Peter Hutterer authored
Build an Arch image that tests a meson build with all build options we support (well, the single one so far). Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 18 Jan, 2021 1 commit
-
-
Peter Hutterer authored
We've been adding to those over the last few years. Not a huge amount but enough that we should stop pretending we don't touch that header. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 10 Oct, 2020 1 commit
-
-
Alan Coopersmith authored
They are fixed length (4 characters), and don't need NUL-terminators. This makes gcc stop warning when they're not NUL-terminated, and instead warn if they are passed to functions expecting NUL-terminated strings. Signed-off-by:
Alan Coopersmith <alan.coopersmith@oracle.com> Reviewed-by:
Matt Turner <mattst88@gmail.com>
-