| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
The DPI value is from the manufacturer documentation, and freq measured
from mouse-dpi-tool
|
| |
|
|
|
|
|
|
| |
The additional rules fix a firmware bug in the en keyboard of Librem notebooks by Purism.
By doing so the break the keyboard with other layouts which do not have the same bug in their firmware.
|
|
|
|
| |
a bunch of entries use 2ch instead of 1ch indentation. Fix that.
|
|
|
|
|
|
|
| |
ST10432-3 tablet
Add a quirk to fix the accelerometer orientation on the
Trekstor Surftab Wintron 10.1 ST10432-3 tablet.
|
|
|
| |
Desktop environments expect f20 hotkey instead of micmute
|
|
|
|
| |
p:0505)
|
|
|
|
| |
Add a quirk to fix the accelerometer orientation on the
Reeder A8iW tablet.
|
|
|
| |
Added the Trekstor Yourbook C11B which is equivalent to Trekstor Primebook C11B.
|
|
|
|
| |
As usual, it seems to be additions and updates, no major removals.
|
|
|
|
| |
I added an entry for Dell Latitude E5510 TouchPad to set up the true size
of the TouchPad (the size is currently over-estimated)
|
| |
|
|
|
|
|
|
| |
The device is very similar to MACH-WX9 in many ways, including this
particular one. Adding these rules gets rid of evdev warnings as buttons
are being pressed on this device.
|
|
|
|
|
|
|
| |
As documented at the top of the file we require the normal property if we have
the horizontal property, and we require the CLICK_ANGLE property if the
CLICK_COUNT property is present. Codify this into the hwdb parser so we can
pick up on it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The script is renamed to match.
Now all targets are named uniformly in a tab-completion-friendly fashion, with
the exception of systemd-update-po which is generated by the i18n module
automatically:
$ ninja -C build -t targets | grep update
systemd-update-po: phony
update-syscall-tables: phony
update-syscall-header: phony
update-hwdb: phony
update-hwdb-autosuspend: phony
update-dbus-docs: CUSTOM_COMMAND
update-man-rules: CUSTOM_COMMAND
|
|
|
|
|
| |
The goal is to have all "update-*" targets named uniformly so that
tab-completion works. The script is renamed to match.
|
|
|
|
|
|
|
|
| |
It is only the Samsung 900X3A which has the alternative function keys.
The 900X3B, 900X4B have the standard Series 9 layout - as defined above.
Note: the 900X4A is not a valid laptop model.
|
|
|
|
|
| |
Add a quirk to fix the accelerometer orientation on
the Jumper Ezpad 7 tablet.
|
|
|
|
|
| |
Add a quirk to fix the accelerometer orientation on the Estar Beauty HD
(marked as model-number MID 7316R on the back) tablet.
|
|
|
|
| |
Add a model-specific entry for Medion Akoya E2228T MD61900 accelerometer to 60-sensor.hwdb so the orientation is detected correctly.
|
|
|
|
|
|
|
|
|
| |
libfprint includes a list of known fingerprint readers that can be
autosuspended. Upstream libfprint generates this file from the USB IDs
registered to drivers and a list of well-known readers that are
currently unsupported.
Closes: #17663
|
|
|
|
|
| |
This makes sense so that we can extend the script to also update other
files.
|
|
|
| |
Add Logitech MX 518 Legendary model to hwdb.
|
| |
|
|
|
|
| |
Added Cube Mix Plus (i18B) Rotation information.
Also Combined the sensor lines with the different Cube i7 stylus models because they use the same ACCEL_MOUNT_MATRIX
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
It has the same code as the Spectre x360 13, but
is located at F8 button instead of F12.
Tested on a 13-ay0xxx model.
|
|
|
| |
Fixes https://gitlab.freedesktop.org/upower/upower/-/issues/128
|
| |
|
|
|
| |
hwdb: Add accelerometer orientation quirk for the MYRIA MY8312
|
|\
| |
| | |
hostnamed: Add "Model" field
|
| |
| |
| |
| | |
See #15493
|
| |
| |
| | |
added support for samsung series 3 np355v4c laptop keyboard
|
|/ |
|
| |
|
|
|
|
|
| |
mappings
On the Dell Inspiron 11 3168 the Fn and Arrow Keys control the Home, End, Page Up and Page Down keys. This commit allows those keys to work correctly.
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the following warning:
```
parse_hwdb.py:120: UserWarning: warn_ungrouped_named_tokens_in_collection: setting results name 'SETTINGS*' on And expression collides with 'HZ' on contained expression
dpi_setting = (Optional('*')('DEFAULT') + INTEGER('DPI') + Suppress('@') + INTEGER('HZ'))('SETTINGS*')
```
Not sure about for the mount_matrix, but LGTM.com warns in that line,
and, adding Group() does not change the parse result.
|
| |
|
|
|
|
|
| |
Only some small changes, because we updated recently. As usual, it seems that there are mostly
additions with a smaller amount of corrections, no big removals.
|
| |
|
|
|
|
| |
(#17659)
|
|
|
|
|
| |
Add a quirk to fix the accelerometer orientation on the
Acer Aspire Switch 10 SW3-016 2-in-1.
|
|
|
|
|
| |
Add a quirk to fix the accelerometer orientation on the
Voyo Winpad A15 tablet.
|
|
|
|
|
| |
Add a quirk to fix the accelerometer orientation on the Lenovo
ThinkPad Yoga 11e 4th gen 360 degree hinges 2-in-1.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Lenovo ThinkPad Yoga 11e 360 degree hinges style 2-in-1s use 2
accelerometers, 1 in the display and 1 in the base.
Kernel work is under way to also export the second accelerometer in
the base as an iio-device; and userspace work is underway to use
both accelerometers on 360 degree hinges style 2-in-1s (with 2 accels)
to figure out the angle between the 2 halves.
So far most orientation-matrix quirks have not cared much about the
Z-axis being correct, but in these 2 accelerometer setups getting
the Z-axis correct is important too.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Akoya E* series
The KIOX010A and KIOX02A ACPI hw-ids (HIDs) are used in 360 degree hinges
style 2-in-1s which have 2 accelerometers, 1 in the display (as usual) and
a second accelerometer in the base.
So far 60-sensor.hwdb has only defined a mount-matrix for the
sensor with the KIOX010A HID, which is the sensor in the display
half of the device. The reason for this is that sofar userspace has
only cared actually used the sensor in the display (for automatic
display rotation. Work is underway to make userspace use both sensors:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/216
Recently an entry was added for the Medion Akoya's E2221T base-sensor,
but that was added to mark it with ACCEL_LOCATION=base and the entry
simply used the identity-matrix for ACCEL_MOUNT_MATRIX since nothing
is using the mount-matrix info for the second accelerometer.
I believe that this entry was added because on some devices the second
accelerometer gets enumerated first and then iio-sensor-proxy will
wrongly use the second sensor for display-rotation, unless it is marked
with ACCEL_LOCATION=base.
Instead of adding info for the second accelerometer on a per device
basis use the same generic dmi matches as used for the first (KIOX010A)
sensor, replacing the special case added for the E2221T and also
update the ACCEL_MOUNT_MATRIX with the actual mount-matrix for the
KIOX020A sensor in the base of these devices.
This was tested on a Medion Akoya E2228T.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
base-accelerometer in 360 degree hinges style 2-in-1s with 2 accelerometers
Document how the mount-matrix for the base-accelerometer must be set on
360 degree hinges style 2-in-1s with 2 sensors (one in the display and
1 in the base).
Note the choice to define the lid being fully closed as an angle of
0 degrees is based on the ACPI tables of devices with a BOSC0200
ACPI device-node describing both sensors. In this case the ACPI
tables contain mount-matrix info (and the kernel will soon support
reading this and exporting it to userspace) and the mount-matrices
defined in these ACPI tables are such that the angle of the G-force
vector measured by the sensors is identical for both sensors when
the laptop's lid is fully closed.
This also feels more natural then defining the laptop being fully
open (180 degrees open) as the home / 0 degree angle position.
|
|
|
|
| |
Follow-up for b0a3a3ff5d80d1605926fbba1d25a0f2448e383c.
|