| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Prompted by #22278.
|
| |
|
|\
| |
| | |
hostname: Allow overriding the chassis type from hwdb
|
| |
| |
| |
| | |
See https://github.com/systemd/systemd/issues/7390#issuecomment-345546127
|
| | |
|
|/ |
|
|
|
|
|
| |
As is currently done in the upstream minipro tool:
https://gitlab.com/DavidGriffith/minipro/-/tree/master/udev
|
|
|
|
| |
Those patterns were always supposed to be uppercase.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The check was added in 77547d5313ea916d2fb64ca5a8812734e9b50f92, but
it doesn't work as expected. Because the second part is wrapped in Optional(),
it would silently "succeed" when the lowercase digits were in the second part:
>>> from parse_hwdb import *
>>> g = 'v' + upperhex_word(4) + Optional('p' + upperhex_word(4))
>>> g.parseString('v04D8pE11C*')
(['v', '04D8', 'p', 'E11C'], {})
>>> g.parseString('v04D8pe11c*')
(['v', '04D8'], {})
The following matches are OK:
usb:v0627p0001:*QEMU USB Keyboard*
usb:v0627p0001:*
usb:v0627p0001*
usb:v0627*
|
|
|
|
| |
Signed-Off-By: Marco Scardovi <marco@scardovi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Asus TF103C misses the home button in its PNP0C40 GPIO resources
causing the button mappings for the volume buttons to be off by one,
leading to the volume-up button sending home button presses and the
volume-down button sending volume-up button presses.
Add a 60-keyboard hwdb entry to correct the mappings. Note this is
split over 2 input devices because the soc_button_array driver
creates separate input devices for power + home and vol up/down.
This is done because power/home act as wakeup buttons where as
the volume buttons do not.
This means that after this fixup the home -> volume-up button
still acts as a wakeup button, there is nothing which can be done
about this without adding a kludge to the kernel which is not
worth the trouble (IMHO).
|
|
|
|
| |
Generated by `meson compile -C build update-hwdb update-hwdb-autosuspend`.
|
|
|
|
| |
Just a small bunch of additions and a naming updates.
|
| |
|
|
|
|
|
| |
As usual, there are mostly additions of new entries, and some spelling
correction and company renames, no big removals.
|
| |
|
|
|
| |
Some HP keyboards (like https://h30434.www3.hp.com/t5/image/serverpage/image-id/203235i01AD626584587DA1?v=v2) have <> between AltGr and left arrow. This add the fix and make it working again
|
| |
|
|
|
|
|
| |
Dell new Privacy feature provide new hardware level privacy protect for users
This patch remaps scancode 0x120001 to key code F20 micmute
|
|
|
|
|
|
|
|
|
| |
In Linux kernel 5.16 prepatch, MOTU Track 16 is newly supported by ALSA
firewire-motu driver.
This commit adds hwdb entry for the device.
Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=411ac2982cb6
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This entry only matches on vid/pid, so the pen event node of the device
would also get assigned the ID_INPUT_TABLET_PAD property - making it
break with libinput.
On top of that, UC-Logic's tablets re-use USB ids, so now we're breaking
multiple devices this way.
To get this device tagged correctly, use libwacom which has the
per-device hwdb entries.
Fixes #17953
This reverts commit 0fbe78ac7a4c5689660b1c1e2c956ffa1a2e4ee5
|
|
|
|
|
|
| |
So that front-ends can ignore them if they wish to.
See https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/4
|
|
|
|
|
| |
The Surface Type Covers are known to support USB autosuspend just fine
(and it's also enabled by default on Windows), so enable it in hwdb.
|
| |
|
|
|
|
| |
Both files were developed in our tree, so they are under the default license.
|
|
|
|
|
| |
#20287 was wrong.
Y Axis was only reversed on Arch Linux because of a problem with iio-sensor-proxy
This restores before the patch.
|
| |
|
|\
| |
| | |
hwdb: Remove intel-hid rfkill mask
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Turns out HP is phasing out hp-wireless in new models, so we need to use
intel-hid for rfkill events.
To have best backward and forward compatibility, the solution is
implemented in userspace:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Kernels >= 5.8 have added new fields to the dmi/id/modalias file in the
middle of the modalias (instead of adding them at the end).
Specifically new ":br<value>:" and (optional) ":efr<value>:" fields have
been added between the ":bd<value>:" and ":svn<value>:" fields.
Note the 5.13.0 and 5.14.0 kernels also added a new ":sku<value>:" field
between the ":pvr<value>:" and ":rvn<value>:" fields, this has been fixed
in later 5.13.y and 5.14.y releases, by moving the sku field to the end:
https://lore.kernel.org/lkml/20210831130508.14511-1-hdegoede@redhat.com/
Unfortunately the same cannot be done for the new br and efr fields since
those have been added more then a year ago and hwdb even already has some
newer entries relying on the new br field being there (and thus not working
with older kernels).
Fix the issue with the br and efr fields through the following changes:
1. Replace any matches on ":br<value>" from newer entries with an '*'
2. Replace "bd<value>:svn<value>" matches with: "bd<value>:*svn<value>"
inserting an '*' where newer kernels will have the new br + efr fields
This makes these matches working with old as well as new kernels.
Link: https://github.com/systemd/systemd/issues/20550
Link: https://github.com/systemd/systemd/pull/20562
|
| |
| |
| |
| |
| | |
Add a quirk for the accelerometer orientation for the
Cyberbook T116 rugged tablet.
|
| |
| |
| |
| |
| | |
Add a quirk for the accelerometer orientation for the
Chuwi Hi10 Plus (CWI527) tablet.
|
| |
| |
| |
| | |
Gemini Lake)
|
| | |
|
| |
| |
| |
| | |
This pulls in a few new devices and adds ID_PERSIST=0.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The USB persist feature allows devices that can retain their state when
powered down to work across suspend/resume. This is in particular useful
for USB drives.
However, the persist feature can get in the way for devices that are
unable to retain their state when power is lost. An example of such
stateful devices are fingerprint readers where USB persist should be
disabled to ensure userspace can detect whether the USB device had a
power loss during system suspend.
This will initially be used by the libfprint autosuspend hwdb.
Closes: #20754
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a related commit to the bug reported in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938259
This adds additional 4 models that without this param, the screen rotates
when the clamshell laptop rotates, which is an unwanted behavior.
This commit also merges entries that needs the same param.
Signed-off-by: Yao Wei (魏銘廷) <yao.wei@canonical.com>
|
|\ \
| | |
| | | |
hwdb: Allow end-users root-less access to USB analysers
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Procotol analyzers are external devices used to capture traffic over a
wire so that it could be analysed. End-users at the console should be
able to access those devices without requiring root access.
This change obsoletes the need to install Total Phase's "Linux drivers",
which are really just udev rules and hotplug usermap files to do that:
https://www.totalphase.com/products/usb-drivers-linux/
|
| | |
| | |
| | |
| | | |
Fix volume control keys for LG Gram
|
| | | |
|
|/ /
| |
| | |
Fixes the keys not creating release events
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Check for "TrackPoint" in the device name and add the
ID_INPUT_POINTINGSTICK property.
In reference to libinput issue:
https://gitlab.freedesktop.org/libinput/libinput/-/issues/651
|
| |
| |
| |
| |
| |
| |
| | |
This commit was done to add sensor rule for Hometech Wi101. Note that this rule might be too general and need fixes. I couldn't test this on any other device since this one is the only one I have.
Co-authored-by: Simeonlps <Simeonlps@users.noreply.github.com>
Signed-off-by: Wind/owZ <windowz414@gnuweeb.org>
|
|/
|
|
|
| |
* Add force-release for HP Omen 15 calculator key.
The key doesn't create release event so I have come up with this fix to make it work properly.
|
| |
|