summaryrefslogtreecommitdiff
path: root/rules.d
Commit message (Collapse)AuthorAgeFilesLines
* meson: Install missing udev ruleJan Janssen2023-01-271-0/+1
|
* udev: also create partition /dev/disk/by-diskseq/ symlinksLennart Poettering2022-12-231-0/+1
|
* rules: add missing line continuationYu Watanabe2022-12-211-1/+1
| | | | | | Fixes a bug introduced by 953c928c24455744d5534679998d129b947a5e04. Fixes #25811.
* udev: rework 60-evdev.rules to be "additive"Zbigniew Jędrzejewski-Szmek2022-12-121-10/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We would execute up to four hwdb match patterns (+ the keyboard builtin): After the first hit, we would skip the other patterns, because of the GOTO="evdev_end" action. 57bb707d48131f4daad2b1b746eab586eb66b4f3 (rules: Add extended evdev/input match rules for event nodes with the same name), added an additional match with ":phys:<phys>:ev:<ev>" inserted. This breaks backwards compatibility for user hwdb patterns, because we quit after the first match. In general hwdb properties are "additive". We often have a general rule that matches a wider class and then some specific overrides. E.g. in this particular case, we have a match for all trackpoints, and then a bunch of model-specific settings. So let's change the rules to try all the match patterns and combine the received properties. We execute builtin-keyboard once at the end, if there was at least one match. Fixes #25698. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2152226. This also impacts other cases which I think would be very confusing for users. Since we quit after a first successful match, if we had e.g. a match for 'evdev:input:b*v*p*' in out database, and the user added a match using 'evdev:name:*', which is the approach we document in the .hwdb files and which users quite often use, it would be silently ignored. What's worse, if we added our 'evdev:input:b*v*p*' match at a later point, user's match would stop working. If we combine all the properties, we get more stable behaviour.
* udev: add safe guard for setting by-id symlinkYu Watanabe2022-11-031-0/+1
| | | | The ID_BUS property is necessary for creating by-id symlinks.
* udev: drop redundant call of usb_id and assignment of ID_USB_INTERFACE_NUMYu Watanabe2022-11-031-2/+0
| | | | | The usb_id builtin command is already called in the above, and the command sets the ID_USB_INTERFACE_NUM property.
* udev: first set properties based on usb subsystemYu Watanabe2022-11-031-2/+3
| | | | | | | | | | After 479da1107a0d4e2f7ef5cd938512b87a0e45f180, the usb_id builtin command does not set ID_SERIAL if ID_BUS is already set. Before the commit, all properties set based on pci bus were overwritten by the usb_id, hence now it is sufficient setting them only when ID_BUS is not set yet. Fixes #25238.
* udev: always create device symlinks for USB disksYu Watanabe2022-10-301-2/+8
| | | | | | | | | Previously, ata_id might not be able to retrieve attributes correctly, and properties from usb_id were used as a fallback. See issue #24921 and PR #24923. To keep backward compatibility, still we need to create symlinks based on USB serial. Fixes #25179.
* udev-builtin-kmod: support to run without argumentsYu Watanabe2022-10-141-1/+1
| | | | | | | | | | | If no module name is provided, then try to load modules based on the device modealias. Previously, MODALIAS property is passed as an argument, but it may contain quotation. Hence, unfortunately the modalias may be modified and cannot load expected modules. Fixes #24715.
* udev/rules: add by-path and by-ibdev links to infiniband verbsLubomir Rintel2022-10-141-0/+12
| | | | | | | | | | The uverbs devices are sequentially numbered and are not guarranteed to stay stable across reboot. At least one good person was disappointed by this, because they couldn't find their device: https://bugzilla.redhat.com/show_bug.cgi?id=2036515 Let's add a few helpful links.
* udev: support by-path devlink for multipath nvme block devicesYu Watanabe2022-09-231-0/+1
| | | | | | | | | | | | | | | If multipath feature is enabled, nvme block devices may belong to the "nvme-subsystem" subsystem, instead of "nvme" subsystem. (What a confusing name...) Then, the syspath is something like the following, /sys/devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1 Hence, we need to find the 'real parent' device, such as /sys/devices/pci0000:00/0000:00:1c.4/0000:3c:00.0/nvme/nvme0 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2031810. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2124964. Replaces #24748.
* udev/rules,hwdb: filter out mostly meaningless default stringsYu Watanabe2022-09-061-2/+3
| | | | | | | | | | | | The filter is generated based on the following results: --- git clone git@github.com:linuxhw/DMI.git cd DMI git grep -h -A2 '^System Information$' | grep 'Manufacturer' | sort | uniq -c | sort -nr | less git grep -h -A2 '^System Information$' | grep 'Product Name' | sort | uniq -c | sort -nr | less --- Closes #24446.
* rules: import previous SYSTEMD_READY state for suspended DM devices and skip ↵Michal Sekletar2022-08-191-0/+6
| | | | | | | | | | | other rules We can't get any FS meta-data from a suspended device. Hence defer making any plugged/unplugged decisions, i.e. we just import whatever was previous state and skip processing all other rules. Thanks Lennart Poettering <lennart@poettering.net> for suggesting this solution.
* udev: hwdb: Add rules to match cros-ec-accel by 'location' sysfs fileAlper Nebi Yasak2022-08-181-0/+11
| | | | | | | | | | | | | The cros-ec-accel devices report their mounting location by the 'label' sysfs file only since Linux v6.0. With earlier kernels, a nonstandard 'location' file reports this, but slightly differently (lid instead of display) [1]. Add udev rules to import the correct hwdb entries based on this 'location' file for cros-ec-accel devices, so that the base-mounted accel matrix has the correct value for older kernels as well. [1] https://kernel.org/doc/Documentation/ABI/testing/sysfs-bus-iio-cros-ec
* udev: hwdb: Match iio sensors based on their labelAlper Nebi Yasak2022-08-181-0/+5
| | | | | | | | | | | | | | | | | | The IIO subsystem exposes a 'label' sysfs file to help userspace better identify its devices [1]. Standardized labels include the sensor type along with its location, including 'accel-base' and 'accel-display'. Most Chrome OS boards have two accelerometers that are indistinguishable except for this label (or a 'location' sysfs file before Linux v6.0), and need different mounting matrix corrections based on their location. Add a udev rule that matches hwdb entries using this label, so we can correct both accelerometers on these devices with hwdb entries. The existing rules and hwdb entries are not modified to keep potential out-of-tree entries working, but new entries in this form will override existing ones. Also add currently standardized labels to parse-hwdb.py. [1] https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-bus-iio
* hwdb: Allow users access to USB serial for analysersBastien Nocera2022-08-091-0/+1
| | | | | | | Allow users at the console access to the USB serial interface for USB analysers. See 9e2dbfef479060ed850ccdd9cd82d3f0cda2b5c0
* udev: add flag to allow disabling blkid probingDarsey Litzenberger2022-07-151-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | This can be useful for users of slow block devices. For example, the persistent-storage rules are needed for USB floppy drives be recognized by udisks2, but the extra blkid calls cause thrashing for 25+ seconds after every disk change. With this change, a user wishing to avoid the extra blkid invocation(s) could create /etc/udev/rules.d/55-floppy-noprobe.rules as follows: # Don't probe PC floppy drives SUBSYSTEM=="block", KERNEL=="fd*", \ ENV{UDEV_DISABLE_PERSISTENT_STORAGE_BLKID_FLAG}="1" # Don't probe USB floppy drives SUBSYSTEM=="block", SUBSYSTEMS=="usb", \ ATTRS{bInterfaceClass}=="08", ATTRS{bInterfaceSubClass}=="04", \ ENV{UDEV_DISABLE_PERSISTENT_STORAGE_BLKID_FLAG}="1" I didn't exclude floppies by default in this change, because floppy devices are also emulated by some BIOSes/hypervisors in some cases, and I don't know how many systems would fail to boot if /dev/disk/by-uuid/* became unavailable for 'floppy disks' on those systems.
* meson: install 70-power-switch.rulesYu Watanabe2022-05-191-0/+3
| | | | | | Fixes a bug introduced by 155078c835a00fed264a7b36b06f709d9b57cb1b. Fixes #23425.
* Add support to set autosuspend delay via hwdbMario Limonciello2022-05-091-0/+4
|
* meson: move vconsole rules to rules.d/Zbigniew Jędrzejewski-Szmek2022-05-052-0/+14
|
* meson: move udev rules to rules.d/Zbigniew Jędrzejewski-Szmek2022-05-055-48/+280
|
* udev: set ID_IGNORE_DISKSEQ for md devicesYu Watanabe2022-04-141-0/+4
|
* udev: do not create disk/by-diskseq symlink when ID_IGNORE_DISKSEQ property ↵Yu Watanabe2022-04-141-1/+1
| | | | is set
* udev: create disk/by-diskseq symlink only when the device has diskseqYu Watanabe2022-04-131-1/+1
| | | | Follow-up for 0d08db7f89ee665a9dcb6dd66c1f9e203192e8ec.
* meson: also allow setting GIT_VERSION via templatesZbigniew Jędrzejewski-Szmek2022-04-051-1/+1
| | | | | | | | | GIT_VERSION is not available as a config.h variable, because it's rendered into version.h during builds. Let's rework jinja2 rendering to also parse version.h. No functional change, the new variable is so far unused. I guess this will make partial rebuilds a bit slower, but it's useful to be able to use the full version string.
* udev: add /dev/disk/by-diskseq symlink for block devicesLennart Poettering2022-04-011-0/+5
| | | | | | | | | | | | | | | | | This adds another symlink for block devices: /dev/disk/by-diskseq/<number> where the number is the diskseq number as exposed by the kernel. It's useful for apps because they can use it to open a device by diskseq, in a way that is safe against device node reuse. I.e. if a device node path like this is passed to an app it could open the device node via the symlink and also parse the diskseq from the path. Once the device is opened it could compare the parsed diskseq with the one returned by BLKGETDISKSEQ on the open node, and if it matches they know they are talking to the right device. Fixes: #22906
* udev: 60-persistent-storage-tape.rules: handle duplicate device IDDavid Bond2022-03-081-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Some SCSI tape devices use the same device ID (NAA registered device designator) for the SCSI tape changer device and the first actual tape device. For example, this one: https://docs.oracle.com/en/storage/tape-storage/storagetek-sl150-modular-tape-library/slofs/bridged-tape-drives.html You must connect the bridged drive to an HBA supporting multiple LUNs (also referred to as LUN scanning). The SL150 Library uses a single SCSI ID and two logical unit numbers (LUN). LUN 0 controls the tape drive and LUN 1 which is configured as a SCSI medium changer device controls the robotics. Data is sent to the remaining LUN on the bridged drive or to LUNs on the other, unbridged drives in the partition, all of which are configured as SCSI sequential-access (tape) devices. This may lead to errors because /dev/tape/by-id symlinks may sometimes point to the st device representing the tape, and sometimes to the sg device representing the changer. Fix this by assigning an increased priority to the tape device, and creating a separate -changer link for the SCSI tape changer. Co-developed-by: Martin Wilck <mwilck@suse.com>
* meson: do not use split() in file listsZbigniew Jędrzejewski-Szmek2022-03-021-25/+24
| | | | | | | | | | | The approach to use '''…'''.split() instead of a list of strings was initially used when converting from automake because it allowed identical blocks of lines to be used for both, making the conversion easier. But over the years we have been using normal lists more and more, especially when there were just a few filenames listed. This converts the rest. No functional change.
* rule: fallback to use board information if product information is not setYu Watanabe2022-01-231-0/+3
|
* rule: make ID_SYSFS_ATTRIBUTE_MODEL also accept product_nameYu Watanabe2022-01-231-2/+5
|
* Revert "udev: Import hwdb matches for USB devices"Zbigniew Jędrzejewski-Szmek2022-01-041-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 94cb45d57f6e94dd4c93bd4706f9be70634bf03f. This rule set up a duplicate import: $ udevadm test /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1.3 ... 2-4.1.3: /usr/lib/udev/rules.d/40-libgphoto2.rules:9 Importing properties from results of builtin command 'usb_id' 2-4.1.3: /usr/lib/udev/rules.d/50-udev-default.rules:13 Skipping builtin 'usb_id' in IMPORT key 2-4.1.3: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'hwdb --subsystem=usb' 2-4.1.3: hwdb modalias key: "usb:v17EFp3054:OneLink+ Giga" 2-4.1.3: /usr/lib/udev/rules.d/50-udev-default.rules:15 Importing properties from results of builtin command 'hwdb 'usb:v17efp3054'' 2-4.1.3: No entry found from hwdb. 2-4.1.3: /usr/lib/udev/rules.d/50-udev-default.rules:15 Failed to run builtin 'hwdb 'usb:v17efp3054'': No data available 2-4.1.3: /usr/lib/udev/rules.d/50-udev-default.rules:52 MODE 0664 except that the existing one was done with uppercase digits and the full match pattern, and the second one was done with lowercase digits. With the previous commit we only have uppercase digits in our match patterns, so we can drop the duplicate import. (Some other projects might have rules that used the lowercase match patterns, and people might have some local rules that did that too. But the second import was only added recently so I think it's better to rip off the bandaid quickly.)
* Enable /dev/sgx_vepc access for the group 'sgx'Jarkko Sakkinen2021-12-121-0/+1
| | | | | | | Enable /dev/sgx_vepc access for the group 'sgx', which allows KVM-backed VMs to host Intel Software Guard eXtension (SGX) enclaves. The upcoming QEMU 6.2 uses /dev/sgx_vepc to reserve portions of Enclave Page Cache (EPC) for VMs. EPC is the reserved physical memory used for hosting enclaves.
* build: preserve correct mode when generating files via jinja2Christian Brauner2021-11-081-2/+1
| | | | | | | | | When using "capture : true" in custom_target()s the mode of the source file is not preserved when the generated file is not installed and so needs to be tweaked manually. Switch from output capture to creating the target file and copy the permissions from the input file. Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
* hwdb: Tag IR cameras as suchwip/hadess/webcamsBastien Nocera2021-10-272-0/+10
| | | | | | So that front-ends can ignore them if they wish to. See https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/4
* docs: Fixing typo in systemd.device man page and README.alexlzhu2021-09-291-1/+1
| | | | | | | | | systemd-udevd.service listens to kernel uevents and is needed for device units to be available. systemd-udevd.service is misspelled as systemd-udev.service in a couple places. Fixing typo.
* hwdb: Permit unsetting power/persist for USB devicesBenjamin Berg2021-09-211-0/+4
| | | | | | | | | | | | | | | | 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
* udev: Import hwdb matches for USB devicesBastien Nocera2021-09-011-0/+1
| | | | | | Import hwdb matches for USB devices (not interfaces) which don't usually have a modalias so that it's possible to, for example, make them available for unprivileged users.
* udev: Fix by-uuid symlink for ubifs volumesTrent Piepho2021-07-021-1/+1
| | | | | | | | | | | | | ubifs volumes have a UUID and the built-in blkid is able to determine it. The disk/by-uuid symlink isn't created because ubifs volumes are not on block devices but on SUBSYSTEM="ubi" devices. See #20071. Allow ubi subsystem devices to be processed by the persistent storage rules too. The kernel device name matching already allows ubi* to pass. The existing rules are sufficient to create the link. The links look like other by-uuid symlinks, for example: /dev/disk/by-uuid/9a136158-585b-4ba4-9b70-cbaf2cf78a1c -> ../../ubi0_1
* Revert "rules: ubi mtd - add link to named partitions"Lennart Poettering2021-07-011-3/+0
| | | | | | | | This reverts commit 7f1e9c806b6915e8020cf3706dc87e1cd37bc2fa, PR #6750 Apparently the rule change never worked, see #20071. Fixes #20071
* udev: remove unsafe characters from ID_SERIAL for nvmeYu Watanabe2021-06-231-2/+2
| | | | Fixes #19309.
* rules.d: Properly quote $env{MODALIAS}Roshan Shariff2021-05-241-1/+1
| | | | | | Add quotes around use of $env{MODALIAS} in rules.d/80-drivers.rules. The modalias can contain whitespace, for example when it is dynamically generated using device or vendor IDs.
* meson: use jinja2 for rules.d templatesZbigniew Jędrzejewski-Szmek2021-05-194-18/+17
|
* Merge pull request #19513 from takaswie/topic/ieee1394-hwdb-entries-for-videoYu Watanabe2021-05-061-5/+0
|\ | | | | hwdb: ieee1394-unit-function: add entries to obsolete existent udev rules for video function
| * hwdb: ieee1394-unit-function: add entry for AV/C device with vendor unique ↵Takashi Sakamoto2021-05-051-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | command set In IEC 61883-1:1998, we can see some values for AV/C device with vendor unique command set in IEC 61883-1:1998. Current udev rule handles it for video. However it brings an issue that the functions in AV/C device are not distinguished just by the content of configuration ROM. In former commit, hardware database was added to describe function type of unit in the node, then udev rules are added to utilize the database. However, we have an request to obsolete existent udev rules by putting enough entries to the database. It should be done carefully. This commit adds entry into hardware database just for backward compatibility. The entry can match to some node and unit unexpectedly. Therefore this commit modifies existent entries to invalidate the effect from added entry. Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
| * hwdb: ieee1394-unit-function: add entry for AV/C device with generic AV/C ↵Takashi Sakamoto2021-05-051-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | command set Typical node of AV/C device has standard content of configuration ROM. This is defined in documentation of 1394 Trading Association. * Configuration ROM for AV/C Devices 1.0 (Dec. 12, 2000, 1394 Trading Association, TA Document 1999027) However, it brings an issue that the functions in AV/C device are not distinguished just by the content of configuration ROM. In former commit, hardware database was added to describe function type of unit in the node, then udev rules are added to utilize the database. However, we have an request to obsolete existent udev rules by putting enough entries to the database. It should be done carefully. This commit adds entry into hardware database just for backward compatibility. The entry can match to some node and unit unexpectedly. Therefore this commit modifies existent entries to invalidate the effect from added entry. Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
| * hwdb: ieee1394-unit-function: add entries for Point Grey camerasTakashi Sakamoto2021-05-051-1/+0
| | | | | | | | | | | | | | | | | | | | | | Point Grey Research, inc. shipped cameras to support IIDC, however some of them are necessarily compliant to IIDC specification in terms of the value of software version field in unit directory of configuration ROM. This commit adds entries for them. Reviewed-by: Damien Douxchamps <damien@douxchamps.net> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
| * hwdb: ieee1394-unit-function: add IIDC generic entriesTakashi Sakamoto2021-05-051-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instrumentation & Industrial Digital Camera (IIDC) specifications are defined by 1394 Trading Association for camera device in IEEE 1394 bus. IIDC2 specifications are defined by joint working group between Japan Industrial Imaging Association (JIIA) and 1394 Trade Association as bus-independent specification. This commit adds entries for the specifications to remove existent udev rules. Supported specifications are listed below: * 1394-based Digital Camera Specification Version 1.04 (Aug. 9, 1996, 1394 Trading Association) * 1394-based Digital Camera Specification Version 1.20 (Jul. 23, 1998, 1394 Trading Association) * IIDC Digital Camera Control Specification Ver.1.30 (Jul. 25, 2000, 1394 Trading Association) * IIDC Digital Camera Control Specification Ver.1.31 (Feb. 2, 2004, 1394 Trading Association, TA Document 2003017) * IIDC Digital Camera Control Specification Ver.1.32 (Jul. 24, 2008, 1394 Trading Association, Document number 2007009) * IIDC2 Digital Camera Control Specification Ver.1.0.0 (Jan 26th, 2012, 1394 Trading Association, TS2011001) * IIDC2 Digital Camera Control Specification Ver.1.1.0 (May 19th, 2015, 1394 Trading Association, TS2015001) Reviewed-by: Damien Douxchamps <damien@douxchamps.net> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
* | udev: make /dev/vfio/vfio 0666Alyssa Ross2021-05-051-0/+2
|/ | | | | | | Quoting Documentation/driver-api/vfio.rst in Linux: > note that /dev/vfio/vfio provides no capabilities on its own and is therefore > expected to be set to mode 0666 by the system
* Merge pull request #19124 from takaswie/topic/fw-audio-entriesLennart Poettering2021-04-231-0/+10
|\ | | | | hwdb/rule: add database and rules for known audio and music unit in IEEE 1394 bus
| * hwdb: add hardware database for unit of IEEE 1394Takashi Sakamoto2021-04-071-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Current udev rules configures group owner of firewire character device to video group, corresponding to nodes in IEEE 1394 in below cases: 1.the node with any unit for any minor version of IIDC version 1 specification defined by 1394 Trading Association 2.the node with any unit for specification defined by Point Grey Research 3.the node with any unit for AV/C device v1.0 defined by 1394 Trading Association 4.the node with any unit for vendor-unique protocol defined by 1394 Trading Association Nevertheless, case 3 and 4 can cover the node with any unit for audio function as well. In the cases, it's convenient to assign audio group. Additionally, some nodes are known to have layout different from the specification defined by 1394 Trading Association. In the case, it's required to add rules specific to them. Furthermore, some nodes have no fields for vendor name and model name in configuration ROM. In the case, it's required to add entries to hardware database for users convenience. For the above reasons, this commit adds rules to use information in hardware database for known units in IEEE 1394. One database entry corresponds to one unit. Two types of key are used to match the unit; customized key from node context, kernel modalias of unit context. The entry has the type of function, at least. Supplementally, it has vendor and model names. For your information, below statements with Python pyparsing module are expected to parse all of the custom key and module alias in the list: ``` subsystem_prefix = pp.Literal('ieee1394:').suppress() hex_to_int = lambda a: int(a[0], 16) node_prefix = pp.Literal('node:').suppress() prefixed_lower_hex = pp.Combine(pp.Literal('0x') + pp.Word(pp.srange('[a-z0-9]'), exact=6)).setParseAction(hex_to_int) ven_in_node = pp.dictOf(pp.Literal('ven'), prefixed_lower_hex) mo_in_node = pp.dictOf(pp.Literal('mo'), prefixed_lower_hex) unit_in_node = pp.Group(prefixed_lower_hex + pp.Literal(':').suppress() + prefixed_lower_hex) units_in_node = pp.Group(pp.Literal('units') + pp.ZeroOrMore(pp.Literal('*')).suppress() + unit_in_node + pp.ZeroOrMore(pp.Literal('*')).suppress()) node_parser = subsystem_prefix + node_prefix + ven_in_node + pp.Optional(mo_in_node) + units_in_node higher_hex = pp.Word(pp.srange('[A-Z0-9]'), exact=8).setParseAction(hex_to_int) ven_in_unit = pp.dictOf(pp.Literal('ven'), higher_hex) mo_literal_in_unit = pp.dictOf(pp.Literal('mo'), higher_hex) mo_in_unit = pp.dictOf(pp.Literal('mo'), higher_hex ^ pp.Literal('*')) sp_in_unit = pp.dictOf(pp.Literal('sp'), higher_hex) ver_in_unit = pp.dictOf(pp.Literal('ver'), higher_hex) unit_parser = subsystem_prefix + ven_in_unit + mo_in_unit + sp_in_unit + ver_in_unit key_parser = node_parser ^ unit_parser ``` Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
View Lorry Controller Status