login: use a hwdb entry for tagging HyperV's fb devices with 'master-of-seat' tag

Graphic devices that don't do DRM and relies on fb devices are now listed in
hwdb. Dedicated udev rules are no more needed.
This commit is contained in:
Franck Bui 2021-07-01 21:34:34 +02:00
parent c0b2e69f88
commit 7802260baa
2 changed files with 9 additions and 3 deletions

View file

@ -18,3 +18,12 @@
# and falls back to vesafb.
fb:pci:v000018CAd00000020*
ID_TAG_MASTER_OF_SEAT=1
#########################################
# HyperV
#########################################
# HyperV currently doesn't do DRM, hence we need to synthesize for HyperV's fb
# device instead.
fb:pci:v00001414d00005353*
ID_TAG_MASTER_OF_SEAT=1

View file

@ -18,9 +18,6 @@ SUBSYSTEM=="graphics", KERNEL=="fb[0-9]*", TAG+="seat"
SUBSYSTEM=="leds", TAG+="seat"
SUBSYSTEM=="backlight", TAG+="seat"
# HyperV currently doesn't do DRM, hence we need to synthesize for HyperV's fb device instead
SUBSYSTEM=="graphics", KERNEL=="fb[0-9]", DRIVERS=="hyperv_fb", TAG+="master-of-seat"
# Allow efifb / uvesafb to be a master if KMS is disabled
SUBSYSTEM=="graphics", KERNEL=="fb[0-9]", IMPORT{cmdline}="nomodeset", TAG+="master-of-seat"