Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
debian/Tweak-the-udev-rules-creator-for-Debian-usage.patch | Tweak the udev rules creator for Debian usage List all devices; automatic power/control only for the non-blacklisted ones; mode and group to all. |
Sebastien Bacher <seb128@ubuntu.com> | no | vendor | 2020-01-10 | |
meson-Do-not-support-drivers-known-to-fail-in-Big-Endian-.patch | meson: Do not support drivers known to fail in Big Endian archs When building in big endian architectures some device tests will fail, as per this we're pretty sure that most of the drivers are not ready to work in big-endian architectures. Since we're aware of this, better to just stop supporting those drivers instead of having each distribution to handle the problem. So, add a list of supported drivers that is filled depending the architecture type we're building on. Keep continue building those drivers since we want to at least test-build them, but do not expose them as libfprint drivers, so if a device in the system uses any of them will be ignored. At the same time, we keep track of the problem, so that we can fix the drivers. Related to #236 |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/216 | 2020-12-10 | |
udev-rules-Print-warning-if-an-ID-is-supported.patch | udev-rules: Print warning if an ID is supported | Benjamin Berg <bberg@redhat.com> | no | 2021-01-19 | ||
udev-rules-Remove-supported-synaptics-devices.patch | udev-rules: Remove supported synaptics devices | Benjamin Berg <bberg@redhat.com> | no | 2021-01-19 | ||
tests-Add-check-that-no-supported-device-is-whitelisted.patch | tests: Add check that no supported device is whitelisted | Benjamin Berg <bberg@redhat.com> | no | 2021-01-19 | ||
udev-hwdb-Prevent-devices-from-being-listed-twice.patch | udev-hwdb: Prevent devices from being listed twice The change to print a warning (for testing purposes) from commit 944e0d03837 (udev-rules: Print warning if an ID is supported) was incorrect because it prevented duplicated to be suppressed if a device is listed by two independent drivers. |
Benjamin Berg <bberg@redhat.com> | no | 2021-01-20 | ||
tests-Add-trailing-newline-to-busname-devname-sysfs-attri.patch | tests: Add trailing newline to busname/devname sysfs attributes libusb 1.0.24 now expects busnum/devnum to be \n terminated. Update the device descriptions accordingly. https://github.com/martinpitt/umockdev/issues/115 |
Benjamin Berg <bberg@redhat.com> | no | https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/240 | 2021-01-21 | |
build-Skip-the-hwdb-test-if-not-all-drivers-are-really-en.patch | build: Skip the hwdb test if not all drivers are really enabled | =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3b83157e9 | 2021-01-21 | |
debian/data-Use-auto-generated-but-hardcoded-autosuspend-rules-f.patch | data: Use auto-generated but hardcoded autosuspend rules file This solves various problems: 1. It stays the same also if some drivers have been disabled 2. It is still checked for its validity by tests 3. It can be auto-generated using a simple command Based on: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/533180a2 |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2021-01-20 |