1. 30 May, 2019 1 commit
  2. 08 Apr, 2013 1 commit
  3. 13 Jun, 2011 1 commit
  4. 31 Mar, 2011 1 commit
  5. 08 Jan, 2011 2 commits
  6. 21 Jun, 2010 1 commit
  7. 31 May, 2010 1 commit
  8. 25 May, 2010 1 commit
    • Stefan Achatz's avatar
      HID: roccat: propagate special events of roccat hardware to userspace · 206f5f2f
      Stefan Achatz authored
      Module roccat is a char device used to report special events of roccat hardware
      to userland. These events include requests for on-screen-display of profile or
      dpi settings or requests for execution of macro sequences that are not stored
      in device. The information in these events depends on hid device implementation
      and contains data that is not available in a single hid event or else hidraw
      could have been used.
      It is inspired by hidraw, but uses only one circular buffer for all readers.
      The device is as generic as possible so that the functionality is usable by all
      (kone and upcomming) roccat device drivers.
      Signed-off-by: default avatarStefan Achatz <erazor_de@users.sourceforge.net>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  9. 19 May, 2010 2 commits
  10. 22 Mar, 2010 1 commit
    • Stefan Achatz's avatar
      HID: add driver for Roccat Kone gaming mouse · 14bf62cd
      Stefan Achatz authored
      This Patch adds support for Kone gaming mouse from Roccat.
      It provides access to profiles, settings, firmware, weight,
      actual settings etc. through sysfs attributes.
      Event handling of this mouse differs from standard hid behaviour
      in that tilt button press is reported in each move event which
      results in strange behaviour if not handled by the driver.
      This is a heavily reworked version of the previously introduced driver.
      The changes include most of the previously raised concerns,
      memory leak and other fixes, code cleanups, adoption of additional
      achieved knowlege about the hardware and is (IMHO) a much better version
      than before even when I exchanged reduced USB-IO with a bigger memory
      I refused to implement one mentioned point:
      Removing the 'just-because-we-can' attributes. Motivation:
      Reading the clipped in weight: I'm no gamer and can't determine the
      usefulness of this feature but if the manufacturer implements such a
      feature it might make sense to someone and I would unwillingly limit the
      functionality besides its such a small feature.
      Reading the actual profile and dpi settings: Here I can testify that one
      can get lost of the actual settings when switching back and forth.
      The manufacturers windows driver has the ability for on-screen-display
      of the values and there is a mouse in the market that has an lcd on the
      underside of it to show these values. So I think this feature makes sense
      not only for me and shouldn't be removed.
      Signed-off-by: default avatarStefan Achatz <erazor_de@users.sourceforge.net>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>