| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
| |
The firmware of the Olimex Teres-I (a DIY laptop kit) seems to have wrong
scancodes.
Fixes #15003.
|
|
|
|
| |
Devices with proximity sensors can specify a near level that
indicates when an object is considered close to the device.
|
| |
|
|
|
|
|
|
|
|
| |
Unlike newer Medion Akoya E* models for which we have a generic
wildcard match, this model uses a somewhat older KIOX0009 accelerometer.
Not only does our generic catch all not match, we also need a different
matrix for this model, so add a model-specific entry for it.
|
| |
|
|
|
|
|
|
|
| |
the modalias reported by udev is acpi:BOSC0200:BOSC0200: but the rules
only matched acpi:BOSC0200:BOSC0200 (without the trailing colon)
change to acpi:BOSC0200* as in other models
|
|
|
|
| |
Model number NES11-C432SSA
|
|
|
|
|
|
|
| |
This was added in ffac30349e9da91dbef7d4e0bf7cef58705c534e in 2017 but didn't
get added to the meson.build thus never actually installing it.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
|
|
|
|
|
|
|
| |
On the WeiHeng P325J laptop, Fn+F2 sends LeftWindow (0xe0 0x5b) +
LeftCtrl (0x1d) + F24 (0x76). Add a quirk to remap the 0x76 to F21 which
toggles the touchpad. The Ctrl + Win part is handled in userspace, e.g
by gnome-settings-daemon here:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/f545950fe
This is analogous to what was done for the T-bao hardware here:
https://github.com/systemd/systemd/commit/d4a5df521d
|
|
|
|
| |
As before, the changes to .hwdb files are mostly additions and company renames.
|
|
|
|
|
|
| |
Extracted from #12654
Fixes: #12654
|
| |
|
| |
|
|
|
|
| |
Add the resolution and range information for Lenovo Ideapad 310S-14ISK Alps touchpad. It provides information for the test case of libinput for Alps devices.
|
|
|
|
| |
Based on https://github.com/systemd/systemd/pull/14296#issuecomment-567159538.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Synaptics Touchpad that comes with the T490 doesn't explicitly set
its resolution, so these lines are needed to provide that, in order to
help the libinput code detect overly large jumps. Since this device
contains buttons under the lower section of the touchpad, large jumps
are common, so having the resolution helps libinput greatly reduce
the number of occurances of pointer jump.
This comes from
https://gitlab.freedesktop.org/libinput/libinput/issues/402.
|
|\
| |
| | |
Add LCD menu key mappings for the Logitech MX5000 and MX5500
|
| |
| |
| |
| |
| | |
python-evdev needs to be rebuilt with new kernel headers. Before that
happens, our test would reject those keys as unknown.
|
| |
| |
| |
| |
| |
| |
| | |
The kernel now has proper evdev codes for the menu buttons below the
small LCD-s builtin to some keyboards.
Add mappings for these buttons on the Logitech MX5000 and MX5500 keyboards.
|
|/ |
|
|
|
|
|
| |
Since up to now all known Akoya E* models have the same Matrix, we assume all
other Akoya E* models work the same.
|
|
|
|
|
| |
Except for the product IDs, the original MX Master appears identical to
the MX Master 2S.
|
| |
|
| |
|
|
|
|
|
| |
Add a quirk to fix the accelerometer orientation on the Thundersoft
TST168 tablet.
|
| |
|
| |
|
|
|
|
| |
Mouse behaviour is unusably slow disregardless of mouse speed settings.
|
| |
|
| |
|
|
|
|
| |
Add a quirk to fix the accelerometer orientation on the Teclast X89 tablet.
|
|
|
|
|
|
| |
Sort 60-sensor.hwdb Teclast entries alphabetically (by model name),
and add a comment with the model name to the few entries which were
missing this.
|
| |
|
|\
| |
| | |
hwdb: add accel sensor entry for Jumper EZpad Go
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit fix the accelerometer orientation on the Jumper EZpad
Go tablet.
The tablet does not have its product name filled in dmi table, make
the match string a bit generic. Here we assume that the use of a
KIOX000A + bios-vendor + chassis-type combo is unique enough to
match the currently available product in Jumper's x86 tablet series.
For future reference, as in 2019, the tablet has a dmialias of:
dmi:bvnAmericanMegatrendsInc.:bvrZB-BI-11.6-SF133AR200-059-J \
:bd05/21/2019:svnjumper:pnEZpad:pvrTobefilledbyO.E.M.:rvnTob \
efilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:c \
vnTobefilledbyO.E.M.:ct31:cvrTobefilledbyO.E.M.:
|
|/ |
|
| |
|
|
|
|
|
| |
As before, the net change seems to be almost only additions, with some
minor removals that seems to be corrections of incomplete entries.
|
|
|
|
|
|
|
|
| |
There is no change in the file right now, but the download seems to work
OK.
It's funny that the biggest company in the world cannot provide a
download link in plain text.
|
|
|
|
|
| |
This laptop uses the accelerometer as a freefall sensor, so mark it as
in base to prevent screen rotation.
|
|
|
|
|
| |
Add a quirk to fix the accelerometer orientation on the Wortmann
Terra Pad 1061 tablet.
|
|
|
|
|
|
|
|
|
|
|
| |
Chromebook keyboards have a top row which generates f1-f10 key codes but
the keys have media symbols printed on them. A simple scan code to key
code mapping to the correct media keys makes the f1-f10 inaccessible. To
properly use the keyboard a custom key code to symbol mapping in xbk is
required (a variant of the chromebook xkb model is already upstream).
Other devices have similar problems.
This commit makes it possible to specify which xkb model should be used
for a specific device by setting XKB_FIXED_MODEL.
|
|
|
|
|
| |
Add sensor orientation quirk for the Medion Akoya E2215T so that
desktop-environments show their graphics the right way up.
|
| |
|
|
|
| |
See issue #13732
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pyparsing 2.3.1/2.4.0 had some changes to grouping of And matches, and as a
result we'd report 0 properties and 0 matches, and not really do any checks.
With this change we get identical behaviour for pyparsing 2.3.1, 2.4.0, 2.4.2:
$ hwdb/parse_hwdb.py
hwdb/60-evdev.hwdb: 72 match groups, 94 matches, 262 properties
hwdb/60-input-id.hwdb: 3 match groups, 3 matches, 4 properties
hwdb/60-keyboard.hwdb: 173 match groups, 256 matches, 872 properties
Keycode KBD_LCD_MENU1 unknown
Keycode KBD_LCD_MENU4 unknown
Keycode KBD_LCD_MENU2 unknown
Keycode KBD_LCD_MENU3 unknown
hwdb/60-sensor.hwdb: 101 match groups, 120 matches, 105 properties
hwdb/70-joystick.hwdb: 2 match groups, 3 matches, 2 properties
hwdb/70-mouse.hwdb: 104 match groups, 119 matches, 123 properties
hwdb/70-pointingstick.hwdb: 8 match groups, 30 matches, 11 properties
hwdb/70-touchpad.hwdb: 6 match groups, 9 matches, 6 properties
|
|
|
|
|
| |
Also, make the pattern more general. There are some plans to add more files
there, let's make sure we don't miss them.
|
|
|
|
|
|
| |
pyparsing sometimes changes behaviour and stops giving matches. This should
allow us to detect such scenario. With this change, parse_hwdb fails with
pyparsing 2.4 on F31.
|
|
As in the parent commit, this makes the name consistent with the
rest of the source tree and the actuall installation path.
|