mirror of
https://github.com/systemd/systemd
synced 2025-10-05 16:03:15 +02:00
We recommend that users create overriddes. This creates the problem that there is no syntax to unset a property. Thus, the user needs to just set the property to "something else" in the override file. But then the blurb saying that "VAR=1" (or "VAR=0" in some cases) is the only allowed value can be confusing. Say that both 0 and 1 can be set, since this documentation is also intended for end users. In our files, we generally don't want the override values anywhere. But we have a test which checks the rvalue, which should be enough.
37 lines
1.0 KiB
Plaintext
37 lines
1.0 KiB
Plaintext
# This file is part of systemd.
|
|
#
|
|
# Database for remote controllable lights that should be accessible to the seat
|
|
# owner, such as Bluetooth or USB lights that are used in conjuction with the
|
|
# computer like streaming lights.
|
|
#
|
|
# The lookup keys are $MODALIAS strings, see udev's hwdb builtin.
|
|
#
|
|
# To add local entries, create a new file
|
|
# /etc/udev/hwdb.d/71-lights-local.hwdb
|
|
# and add your rules there. To load the new rules execute (as root):
|
|
# systemd-hwdb update
|
|
# udevadm trigger /dev/…
|
|
#
|
|
# If your changes are generally applicable, send them as a pull request to
|
|
# https://github.com/systemd/systemd
|
|
# or create a bug report on https://github.com/systemd/systemd/issues and
|
|
# include your new rules, a description of the device, and the output of
|
|
# udevadm info
|
|
# for the device.
|
|
#
|
|
# Allowed properties are:
|
|
# ID_AV_LIGHTS=0|1
|
|
|
|
################
|
|
# Logitech
|
|
################
|
|
# Litra Beam
|
|
bluetooth:v046dpc901*
|
|
usb:v046dpc901*
|
|
ID_AV_LIGHTS=1
|
|
|
|
# Litra Glow
|
|
bluetooth:v046dpc900*
|
|
usb:v046dpc900*
|
|
ID_AV_LIGHTS=1
|