Announcement

Collapse
No announcement yet.

Logitech High Resolution Scrolling Support Dropped From Linux 4.20

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Logitech High Resolution Scrolling Support Dropped From Linux 4.20

    Phoronix: Logitech High Resolution Scrolling Support Dropped From Linux 4.20

    Yet more fallout from the Linux 4.20 development kernel is over the newly-added Logitech "high resolution scrolling" functionality that is now being disabled until a better solution is in place...

    http://www.phoronix.com/scan.php?pag...olling-Dropped

  • #2
    Typos:

    Originally posted by phoronix View Post
    standard behavior offered for Logitech miceo n Linux up ot this point.
    Originally posted by phoronix View Post
    It turns out that this high resolution scorlling broke

    Comment


    • #3
      Contribute mouse support to libratbag, you need to run "lsusb" to get the USB device identifier for your mouse, then create a device configuration file.

      An example file is available at:
      https://github.com/libratbag/libratb...device.example

      Comment


      • #4
        Originally posted by uid313 View Post
        Contribute mouse support to libratbag, you need to run "lsusb" to get the USB device identifier for your mouse, then create a device configuration file.

        An example file is available at:
        https://github.com/libratbag/libratb...device.example
        This is kernel-level stuff, not really much to do with configuration (though there is a little bit that should go into libratbag, for turning on HID++ 2).

        Comment


        • #5
          Peter Hutter has posted a couple of updates to his patch-set that purportedly fix the compatibility with older Microsoft mice. I've wrapped up a bundle on lore.kernel.org's Patchwork instance that folds in the newer patches. Hopefully they're more workable (and the .mbox applies cleanly on your kernel checkout!).

          Comment


          • #6
            I really wonder what conflicted. Since this only detected Logitech mice, how would it conflict with MS stuff?

            Did the auto-detect code do something bad?

            Comment

            Working...
            X