systemd/rules.d/60-drm.rules

# do not edit this file, it will be overwritten on update

ACTION!="remove", SUBSYSTEM=="drm", SUBSYSTEMS=="pci|usb|platform", IMPORT{builtin}="path_id"

# by-path
KERNEL=="card*",     ENV{ID_PATH}=="?*",                   SYMLINK+="dri/by-path/$env{ID_PATH}-card"
KERNEL=="card*",     ENV{ID_PATH_WITH_USB_REVISION}=="?*", SYMLINK+="dri/by-path/$env{ID_PATH_WITH_USB_REVISION}-card"
KERNEL=="controlD*", ENV{ID_PATH}=="?*",                   SYMLINK+="dri/by-path/$env{ID_PATH}-control"
KERNEL=="controlD*", ENV{ID_PATH_WITH_USB_REVISION}=="?*", SYMLINK+="dri/by-path/$env{ID_PATH_WITH_USB_REVISION}-control"
KERNEL=="renderD*",  ENV{ID_PATH}=="?*",                   SYMLINK+="dri/by-path/$env{ID_PATH}-render"
KERNEL=="renderD*",  ENV{ID_PATH_WITH_USB_REVISION}=="?*", SYMLINK+="dri/by-path/$env{ID_PATH_WITH_USB_REVISION}-render"
rules: load path_id on DRM devices The path_id-builtin provides useful unique aliases for DRM devices. If we want to configure DRM render-nodes for compositors, we want to avoid storing the whole sys-path in configuration files. Hence, allow users to store the short PATH_ID instead. Load path_id-builtin unconditionally on DRM devices now to always provide this alias. 2013-11-03 16:01:20 +04:00			`# do not edit this file, it will be overwritten on update`

rules: simply 60-drm.rules We don't need any GOTO, if we merge all matches into a single line. 2013-11-03 19:17:14 +04:00			`ACTION!="remove", SUBSYSTEM=="drm", SUBSYSTEMS=="pci\|usb\|platform", IMPORT{builtin}="path_id"`
rules: add persistent by-path drm rules (#5337) 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> 2017-02-14 12:18:27 +03:00
			`# by-path`
udev: add USB revision in ID_PATH xHCI host controller may register two (or more?) USB root hubs for USB 2.0 and USB 3.0, and devices under the hubs may have same ID_PATH. So, to avoid the conflict, let's introduce ID_PATH_WITH_USB_REVISION that includes the USB revision. Closes #19406. 2023-05-01 20:28:35 +03:00			`KERNEL=="card", ENV{ID_PATH}=="?", SYMLINK+="dri/by-path/$env{ID_PATH}-card"`
			`KERNEL=="card", ENV{ID_PATH_WITH_USB_REVISION}=="?", SYMLINK+="dri/by-path/$env{ID_PATH_WITH_USB_REVISION}-card"`
			`KERNEL=="controlD", ENV{ID_PATH}=="?", SYMLINK+="dri/by-path/$env{ID_PATH}-control"`
			`KERNEL=="controlD", ENV{ID_PATH_WITH_USB_REVISION}=="?", SYMLINK+="dri/by-path/$env{ID_PATH_WITH_USB_REVISION}-control"`
			`KERNEL=="renderD", ENV{ID_PATH}=="?", SYMLINK+="dri/by-path/$env{ID_PATH}-render"`
			`KERNEL=="renderD", ENV{ID_PATH_WITH_USB_REVISION}=="?", SYMLINK+="dri/by-path/$env{ID_PATH_WITH_USB_REVISION}-render"`