summaryrefslogtreecommitdiffstats
path: root/rules (follow)
Commit message (Collapse)AuthorAgeFilesLines
* meson: reindent all files with 8 spacesZbigniew Jędrzejewski-Szmek2017-04-241-29/+27
| | | | | | | The indentation for emacs'es meson-mode is added .dir-locals. All files are reindented automatically, using the lasest meson-mode from git. Indentation should now be fairly consistent.
* meson: build systemd using mesonZbigniew Jędrzejewski-Szmek2017-04-241-0/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's crucial that we can build systemd using VS2010! ... er, wait, no, that's not the official reason. We need to shed old systems by requring python 3! Oh, no, it's something else. Maybe we need to throw out 345 years of knowlege accumulated in autotools? Whatever, this new thing is cool and shiny, let's use it. This is not complete, I'm throwing it out here for your amusement and critique. - rules for sd-boot are missing. Those might be quite complicated. - rules for tests are missing too. Those are probably quite simple and repetitive, but there's lots of them. - it's likely that I didn't get all the conditions right, I only tested "full" compilation where most deps are provided and nothing is disabled. - busname.target and all .busname units are skipped on purpose. Otherwise, installation into $DESTDIR has the same list of files and the autoconf install, except for .la files. It'd be great if people had a careful look at all the library linking options. I added stuff until things compiled, and in the end there's much less linking then in the old system. But it seems that there's still a lot of unnecessary deps. meson has a `shared_module` statement, which sounds like something appropriate for our nss and pam modules. Unfortunately, I couldn't get it to work. For the nss modules, we need an .so version of '2', but `shared_module` disallows the version argument. For the pam module, it also didn't work, I forgot the reason. The handling of .m4 and .in and .m4.in files is rather awkward. It's likely that this could be simplified. If make support is ever dropped, I think it'd make sense to switch to a different templating system so that two different languages and not required, which would make everything simpler yet. v2: - use get_pkgconfig_variable - use sh not bash - use add_project_arguments v3: - drop required:true and fix progs/prog typo v4: - use find_library('bz2') - add TTY_GID definition - define __SANE_USERSPACE_TYPES__ - use join_paths(prefix, ...) is used on all paths to make them all absolute v5: - replace all declare_dependency's with [] - add more conf.get guards around optional components v6: - drop -pipe, -Wall which are the default in meson - use compiler.has_function() and compiler.has_header_symbol instead of the hand-rolled checks. - fix duplication in 'liblibsystemd' library name - use the right .sym file for pam_systemd - rename 'compiler' to 'cc': shorter, and more idiomatic. v7: - use ENABLE_ENVIRONMENT_D not HAVE_ENVIRONMENT_D - rename prefix to prefixdir, rootprefix to rootprefixdir ("prefix" is too common of a name and too easy to overwrite by mistake) - wrap more stuff with conf.get('ENABLE...') == 1 - use rootprefix=='/' and rootbindir as install_dir, to fix paths under split-usr==true. v8: - use .split() also for src/coredump. Now everything is consistent ;) - add rootlibdir option and use it on the libraries that require it v9: - indentation v10: - fix check for qrencode and libaudit v11: - unify handling of executable paths, provide options for all progs This makes the meson build behave slightly differently than the autoconf-based one, because we always first try to find the executable in the filesystem, and fall back to the default. I think different handling of loadkeys, setfont, and telinit was just a historical accident. In addition to checking in $PATH, also check /usr/sbin/, /sbin for programs. In Fedora $PATH includes /usr/sbin, (and /sbin is is a symlink to /usr/sbin), but in Debian, those directories are not included in the path. C.f. https://github.com/mesonbuild/meson/issues/1576. - call all the options 'xxx-path' for clarity. - sort man/rules/meson.build properly so it's stable
* rules: add a rule to set /dev/kvm access mode and ownership (#5597)Zbigniew Jędrzejewski-Szmek2017-03-272-0/+3
| | | | | | | | | | | | | | | | | | Kernel default mode is 0600, but distributions change it to group kvm, mode either 0660 (e.g. Debian) or 0666 (e.g. Fedora). Both approaches have valid reasons (a stricter mode limits exposure to bugs in the kvm subsystem, a looser mode makes libvirt and other virtualization mechanisms work out of the box for unprivileged users over ssh). In Fedora the qemu package carries the relevant rule, but it's nicer to have it in systemd, so that the permissions are not dependent on the qemu package being installed. Use of packaged qemu binaries is not required to make use of /dev/kvm, e.g. it's possible to use a self-compiled qemu or some alternative. https://bugzilla.redhat.com/show_bug.cgi?id=1431876 To accomodate both approaches, add a rule to set the mode in 50-udev-default.rules, but allow the mode to be overridden with a --with-dev-kvm-mode configure rule. The default is 0660, as the (slightly) more secure option.
* rules: allow SPARC vdisk devices when identifying CD drives (#5599)John Paul Adrian Glaubitz2017-03-201-1/+1
|
* rules: set ID_BUS=bluetooth for any device with id/bustype attr of 0x0005 ↵Peter Hutterer2017-03-071-0/+2
| | | | | | | | | | | | (#5539) Not all bluetooth devices come through the bluetooth subsystem and those that don't currently lack the ID_BUS=bluetooth env. This again fails to apply udev rules and/or hwdb entries that rely on the bluetooth bustype to be set. Fix this by checking the attribute id/bustype on the device instead of just the subsystem. Fixes #4566
* rules: allow quirks for platform input accelerometersThomas Hindoe Paaboel Andersen2017-03-031-0/+4
|
* udev: Allow quirks for ACPI input accelerometersDaniel Drake2017-03-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The existing accelerometer rules only support IIO devices, however iio-sensor-proxy can also work with accelerometers made available through the input (evdev) subsystem. In this case I am working with an accelerometer input device backed by an ACPI driver for which the hierarchy is: - ACCE0001 (ACPI device) -> input8 -> event7 We want the mount matrix (from hwdb) to be applied to both input8 and event7. However, to match in 60-sensor.hwdb, we need to be working with the modalias of the parent device (ACCE0001), and it is tricky to access that when processing the input8 device which has it's own modalias. Instead of working directly with modalias, this ACPI-specific rule uses the "hid" attribute to reconstruct the ACPI modalias. Since input and event devices do not provide a hid attribute we will always get this from the ACPI parent. The modalias is constructed according to the definition in the kernel's Documentation/acpi/namespace.txt and create_pnp_modalias(). We will only use the first _CID/_HID value available, i.e. in some cases we will only reconstruct the first part of the modalias, but that should be enough granularity for our needs.
* udev: Use parent bus id for virtio disk builtin path-id (#5500)Viktor Mihajlovski2017-03-011-0/+4
| | | | | | | | | | | | | | | | | | | | | | | The builtin path id for virtio block devices has been changed to use the bus id without a prefix "virtio-pci" to be compatible with all virtio transport types. In order to not break existing setups, the by-path symlinks for virtio block devices on the PCI bus are reintroduced by udev rules. The virtio-pci symlinks are considered to be deprecated and should be replaced by the native PCI symlinks. Example output for a virtio disk in PCI slot 7: $ ls /dev/disk/by-path pci-0000:00:07.0 pci-0000:00:07.0-part1 virtio-pci-0000:00:07.0 virtio-pci-0000:00:07.0-part1 See also [1] https://lists.freedesktop.org/archives/systemd-devel/2017-February/038326.html [2] https://lists.freedesktop.org/archives/systemd-devel/2017-March/038397.html This reverts f073b1b but keeps the same symlinks for compatibility.
* udev rules: add udev rule to create /dev/ptp_kvm (#5495)Lennart Poettering2017-02-281-0/+2
| | | | | | | | Its necessary to specify the KVM PTP device name in userspace. In case a network card with PTP device is assigned to the guest, it might be the case that KVM PTP gets /dev/ptp0 instead of /dev/ptp1. Fix a device name for the KVM PTP device.
* Export NVMe WWID udev attribute (#5348)Keith Busch2017-02-171-0/+1
| | | | | | We need this for multipath support without relying on NVMe to SCSI translations. Signed-off-by: Keith Busch <keith.busch@intel.com>
* rules: add persistent by-path drm rules (#5337)Marc-Andre Lureau2017-02-141-0/+5
| | | | | | | | | | Create persistent symlinks for DRM devices, ex: /dev/dri/by-path/pci-0000:00:02.0-card -> /dev/dri/card1 /dev/dri/by-path/pci-0000:00:02.0-render -> /dev/dri/renderD129 etc... This allows to configure DRM device usage with stable paths. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
* rules: Add extended evdev/input match rules for event nodes with the same nameHans de Goede2017-02-121-0/+4
| | | | | | | | | | | | | | | | Sometimes a system may have 2 input event nodes with the same name where we only want to apply keyboard hwdb rules to 1 of the 2 devices. This problem happens e.g. on devices where the soc_button_array driver is used (e.g. intel atom based tablets) which registers 2 event nodes with the name "gpio-keys". This commit adds a new extended match rule which extends the match to also check $attr{phys} and $attr{capabilities/ev}, allowing to differentiate between devices with an identical name. Suggested-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
* rules: allow systemd to manage UBI volumes (#5214)Mirza Krak2017-02-031-0/+2
| | | | UBI is a software layer on top of MTD devices that is used with flash chips.
* gpt-auto-generator: support LUKS encrypted root partitionsLennart Poettering2016-12-212-3/+5
| | | | | | | Previously, we supported GPT auto-discovery for /home and /srv, but not for the root partition. Add that, too. Fixes: #859
* core: make mount units from /proc/self/mountinfo possibly bind to a device ↵Franck Bui2016-12-161-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | (#4515) Since commit 9d06297, mount units from mountinfo are not bound to their devices anymore (they use the "Requires" dependency instead). This has the following drawback: if a media is mounted and the eject button is pressed then the media is unconditionally ejected leaving some inconsistent states. Since udev is the component that is reacting (no matter if the device is used or not) to the eject button, users expect that udev at least try to unmount the media properly. This patch introduces a new property "SYSTEMD_MOUNT_DEVICE_BOUND". When set on a block device, all units that requires this device will see their "Requires" dependency upgraded to a "BindTo" one. This is currently only used by cdrom devices. This patch also gives the possibility to the user to restore the previous behavior that is bind a mount unit to a device. This is achieved by passing the "x-systemd.device-bound" option to mount(8). Please note that currently this is not working because libmount treats the x-* options has comments therefore they're not available in utab for later application retrievals.
* rules: identify internal sound cards on platform bus (#4893)Daniel Drake2016-12-151-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | We have a system which has the HDMI audio capability internally, but pulseaudio is not giving it a very high priority compared to e.g. USB sound cards. The sound device appears on the platform bus and it is not currently tagged with any form factor information. It seems safe to assume that any sound card that is directly on the platform bus is of internal form factor, but we must be careful because udev rules will match all parent devices, not just the immediate parent, and you will frequently encounter setups such as: Platform bus -> USB host controller -> USB sound card In that case, SUBSYSTEMS==platform would match even though we're clearly working with an external USB sound card. In order to detect true platform devices here, we rely on the observation that if any parent devices of the sound card are PCI, USB or firewire devices, then this sound card cannot directly connected to the platform bus. Otherwise, if we find a parent device on the platform bus, we assume this is an internal sound card connected directly to the platform bus.
* udev: Add rules for accelerometer orientation quirksBastien Nocera2016-12-101-0/+10
| | | | | | | | | | | | | | | | | | | This commit adds a rules file to extract the properties from hwdb to set on i2c IIO devices. This is used to set the ACCEL_MOUNT_MATRIX property on IIO devices, to be consumed by iio-sensor-proxy or equivalent daemon. The hwdb file contains documentation on how to write quirks. Note however that mount information is usually exported in: - the device-tree for ARM devices - the ACPI DSDT for Intel-compatible devices but currently not extracted by the kernel. Also note that some devices have the framebuffer rotation that changes between the bootloader and the main system, which might mean that the accelerometer is then wrongly oriented. This is a missing feature in the i915 kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=94894 which needs to be fixed, and won't require quirks.
* rules: consider MMC device partitions with partition number > 9 (#4831)Kieran Colford2016-12-061-1/+1
| | | Add entries for extra partitions found on MMC devices (common in Chromebooks).
* rules: add persistent links for nbd devices (#4785)Martin Pitt2016-12-011-1/+1
| | | https://bugs.debian.org/837999
* rules: introduce disk/by-id (model_serial) symlinks for NVMe drives (#3974)Michal Sekletar2016-08-171-0/+6
| | | | | | | | $ ls -l /dev/disk/by-id/nvme* lrwxrwxrwx. 1 root root 13 Aug 17 04:25 /dev/disk/by-id/nvme-HUSPR3216AHP301_STM0001B6780 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Aug 17 04:25 /dev/disk/by-id/nvme-HUSPR3216AHP301_STM0001B6780-part1 -> ../../nvme0n1p1 https://github.com/systemd/systemd/issues/1453 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=779ff75617099f4defe14e20443b95019a4c5ae8
* rules: make sure always set at least one property on rfkill devicesLennart Poettering2016-07-201-2/+1
| | | | | | | | | | | | | | | | The rfkill service waits for rfkill device initialization as reported by udev_device_is_initialized(), and if that is never reported it might dead-lock. However, udev never reports completed initialization for devices that have no properties or tags set. For some rfkill devices this might be the case, in particular those which are connected to exotic busses, where path_id returns nothing. This patch simply sets the SYSTEM_RFKILL property on all rfkill devices, to ensure that udev_device_is_initialized() always reports something useful and we don't dead-lock. Fixes: #2745
* rules: UDEV_DISABLE_PERSISTENT_STORAGE_RULES_FLAG property (#3714)Rusty Bird2016-07-152-0/+2
| | | | | | | | | | | | Sometimes, the persistent storage rules should be skipped for a subset of devices. For example, the Qubes operating system prevents dom0 from parsing untrusted block device content (such as filesystem metadata) by shipping a custom 60-persistent-storage.rules, patched to bail out early if the device name matches a hardcoded pattern. As a less brittle and more flexible alternative, this commit adds a line to the two relevant .rules files which makes them test the value of the UDEV_DISABLE_PERSISTENT_STORAGE_RULES_FLAG device property, modeled after the various DM_UDEV_DISABLE_*_RULES_FLAG properties.
* rules: block: add support for pmem devices (#3683)bgbhpe2016-07-082-2/+2
| | | | | | | | | | | | | | Persistent memory devices can be exposed as block devices as /dev/pmemN and /dev/pmemNs. pmemN is the raw device and is byte-addressable from within the kernel and when mmapped by applications from a DAX-mounted file system. pmemNs has the block translation table (BTT) layered on top, offering atomic sector/block access. Both pmemN and pmemNs are expected to contain file systems. blkid(8) and lsblk(8) seem to correctly report on pmemN and pmemNs. systemd v219 will populate /dev/disk/by-uuid/ when, for example, mkfs is used on pmem, but systemd v228 does not. Add pmem to the whitelist.
* hwdb: add a 70-touchpad.hwdb to tag internal vs external touchpadsPeter Hutterer2016-07-011-0/+13
| | | | | | | | Add a new key ID_INPUT_TOUCHPAD_INTEGRATION=internal|external so we have a single source for figuring out which touchpads are built-in. Fairly simple approach: bluetooth is external, usb is external unless it's an Apple touchpad. Everything else is internal.
* rules: set ID_BUS for bluetooth, rmi and i8042Peter Hutterer2016-07-011-1/+3
| | | | | | | | Something has to so we can have udev rules rely on this. Right now the ID_BUS setting is inconsistent: usb is set, ata and pci are set, bluetooth is not set, rmi is too new to be featured. 70-mouse even relied on bluetooth even though it was never set
* rules: block - add scm block devices to whitelist (#3494)Lennart Poettering2016-06-101-1/+1
| | | | | | | | Since the introduction of the whitelist in 60-persistent-storage.rules block device symlinks are no longer created for scm block devices. Add scm to the whitelist. Signed-off-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
* rules: add /dev/disk/by-partuuid symlinks also for dos partition tablesUwe Kleine-König2016-05-191-1/+1
| | | | | | | blkid reports PARTUUID values also for partitions that are defined by a dos partitioning scheme. Instead of limiting the partitioning scheme to "gpt or dos" just drop the test for the partitioning scheme and trust blkid to do the right thing.
* rules: add NVMe rules (#3136)Ming Lin2016-04-291-0/+4
| | | | | | | | | | | Add NVMe rules using the "wwid" attribute. root@target:~# cat /sys/block/nvme0n1/wwid eui.3825004235000591 root@target:~# ls /dev/disk/by-id/ -l |grep nvme lrwxrwxrwx 1 root root 13 Apr 27 16:08 nvme-eui.3825004235000591 -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Apr 27 16:08 nvme-eui.3825004235000591-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Apr 27 16:08 nvme-eui.3825004235000591-part2 -> ../../nvme0n1p2
* Mark nbd as inactive until connected (#2422)Wouter Verhelst2016-04-181-2/+2
| | | | | | | | | | | | | | | | | | | Currently, 99-systemd.rules.in contains a line for network block devices, which mark them as inactive until the first change event, and as active from then on forward. This is not correct. A network block device can be connected or disconnected; this state is signalled by the presence or absense of a "pid" file, which contains the PID of the nbd client userspace process that started the connection. Update the rules file so that it checks for the presence of that file to decide what to set SYSTEMD_READY to. Note that current kernels do issue a change event upon connecting the device, but not yet upon disconnecting. While it's possible to wait until that's been fixed, the behaviour of the rule with TEST!="pid" in the absence of a proper uevent is exactly the same as the behaviour of the old rule; so it should be safe to apply now. Signed-off-by: Wouter Verhelst <w@uter.be>
* rules: set SYSTEMD_READY=0 on DM_UDEV_DISABLE_OTHER_RULES_FLAG=1 only with ↵Lukáš Nykrýn2016-04-121-1/+1
| | | | | | | | | | | | ADD event (#2747) The "SYSTEMD_READY=0" will cause automatic unmount of mountpoint that is on top of such DM device if this is used with multipath which sets DM_UDEV_DISABLE_OTHER_RULES_FLAG in case we have a CHANGE event thatcomes after DM multipath device reload when one of the paths is down or up. See https://bugzilla.redhat.com/show_bug.cgi?id=1312011
* rfkill: rework and make it listen on /dev/rfkillLennart Poettering2015-10-011-1/+2
| | | | | | | | | | | | | | With this rework we introduce systemd-rfkill.service as singleton that is activated via systemd-rfkill.socket that listens on /dev/rfkill. That way, we get notified each time a new rfkill device shows up or changes state, in which case we restore and save its current setting to disk. This is nicer than the previous logic, as this means we save/restore state even of rfkill devices that are around only intermittently, and save/restore the state even if the system is shutdown abruptly instead of cleanly. This implements what I suggested in #1019 and obsoletes it.
* UML: Fix block device setupThomas Meyer2015-08-091-1/+1
| | | User mode linux block devices start with ubd, e.g. ubda, ubdb, etc..
* rules: block - add dasd to whitelistKay Sievers2015-07-051-1/+1
|
* Merge pull request #387 from kaysievers/wipTom Gundersen2015-06-291-3/+0
|\ | | | | udev: Remove accelerometer helper
| * udev: Remove accelerometer helperBastien Nocera2015-06-271-3/+0
| | | | | | | | It's moved to the iio-sensor-proxy D-Bus service.
* | Process cciss devicesCédric Delmas2015-06-291-1/+1
|/ | | Do not skip the persistent storage rules for cciss devices
* Merge pull request #353 from kaysievers/hidGreg Kroah-Hartman2015-06-261-36/+0
|\ | | | | rules: remove all power management from udev
| * rules: remove all power management from udevKay Sievers2015-06-241-36/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is not udev's task to apply any of these setting that way, or from udev rules files. Things need to be sortet out in the kernel, or explicit whitelist can possibly be added to the hardware database. Until that is sorted out, and general agreement, udev is not willing to maintain any such lists or power management settings in general. "Thanks for digging this out! I thought my Kinesis keyboard got broken and ordered a new one, only to find out that the new one doesn't work as well. I'm not sure whether we should start collecting a blacklist of keyboards which don't work with USB autosuspend, or rather a whitelist? Or revert this wholesale?" https://github.com/systemd/systemd/issues/340
* | Revert "hwdb: add a touchpad hwdb"Peter Hutterer2015-06-261-12/+0
|/ | | | | | | | | | | | The main purpose of this hwdb was to tag touchpads that have the physical trackstick buttons wired to the touchpad (Lenovo Carbon X1 3rd, Lenovo *50 series). This hwdb is not required on kernels 4.0 and above, the kernel now re-routes button presses through the trackstick's device node. Userspace does not need to do anything. See kernel commit cdd9dc195916ef5644cfac079094c3c1d1616e4c. This reverts commit 001a247324b44c0e0b8fdba41a6fc66e7465b8b6.
* rules: re-add cciss rulesAlex Crawford2015-06-111-2/+3
| | | | | The original commit (1aff206) doesn't explain why these were removed. This adds them back since they are in fact needed.
* rules: whitelist xvd* devicesAlex Crawford2015-06-092-2/+2
| | | | Xen disks need to be whitelisted as well.
* Add /dev/xvd* to 60-persistent-storage whitelistEd Swierk2015-06-031-1/+1
| | | | | Without this, systemd-udevd does not create persistent storage symlinks for xen block devices.
* udev: Bring back persistant storage symlinks for bcacheDavid Mohr2015-06-011-1/+1
| | | | https://bugs.debian.org/787367
* rules: restore block watch after CHANGE eventsTom Gundersen2015-05-301-1/+1
| | | | | When processing an event, the watch is disabled, make sure it is restorted after a CHANGE event has been processed.
* rules: fix typo in block watch ruleTom Gundersen2015-05-301-1/+1
| | | | | The intention was to turn this rule from using a blacklist to a whitelist, but there was a stray '!'.
* rules: Add more firewire properties for sound, to be closer to USB and PCIAdam Goode2015-04-231-3/+6
| | | | | | | | | USB and PCI soundcards have a nice set of ID_* properties. It would be handy for firewire soundcards to have the same. Note that this removes the explicit setting of ID_ID in the firewire conditional. Because we are now setting ID_SERIAL, ID_ID will come from later in the file.
* rules: Don't use ALSA card id in ID_IDAdam Goode2015-04-231-2/+2
| | | | | | | | | | | | | | | | | The ALSA id sysattr is generated by the sound subsystem and is not a stable identifier. It is generated though some string manipulation then made unique if there is a conflict. This means that it is enumeration-dependent and shouldn't be used for ID_ID. If ID_ID is supposed to be system-unique, it is not already since for firewire it is generated from the guid and there are broken firewire devices that have duplicate guids across devices. This is tracked for PulseAudio at https://bugs.freedesktop.org/show_bug.cgi?id=90129. This is essentially a revert of systemd ed1b2d9fc7d5c5bfe2a67b0b8ff9e5ea8694268e.
* rules: finish incomplete renameZbigniew Jędrzejewski-Szmek2015-04-121-1/+1
| | | | Fixup for 51c0c2869845a058268d54c3111d55d0dd485704.
* rules: fix tests for removable stateMatthew Garrett2015-04-111-3/+3
| | | | | | | We only care about whether our direct parent is removable, not whether any further points up the tree are - the kernel will take care of policy for those itself. This enables autosuspend on devices where the root hub reports that its removable state is unknown.
* udev: builtin-keyboard: add support for EVDEV_ABS_*Peter Hutterer2015-04-112-19/+19
| | | | | | | | | | | | | | | | | | | | | | | | | Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 01:35:41 +0100