Devices usually do not advertise their resolution and libinput relies on the udev property MOUSE_DPI for this information.[1]
It seems that #libinput will first try to find the recommended value of the device, and if that fails, will use the hard-coded value, right? No! libinput directly uses the hard-coded value and systemd-udevd only provides fixed MOUSE_DPI. Neither libinput nor #systemd-udevd has the code to read #DPI from the HID Report Descriptor.
=> More informations about this toot | View the thread | More toots from coelacanthus@yuuta.moe
=> View libinput tag | View systemd tag | View dpi tag This content has been proxied by September (3851b).Proxy Information
text/gemini