1. 15 5月, 2009 1 次提交
  2. 13 5月, 2009 1 次提交
    • B
      HID: Wacom Graphire Bluetooth driver · ca2dcd40
      Bastien Nocera 提交于
      Based on the work by Andrew Zabolotny, an HID driver for the Bluetooth
      Wacom tablet. This is required as it uses a slightly different
      protocols from what's currently support by the drivers/input/wacom*
      driver, and those only support USB.
      
      A user-space patch is required to activate mode 2 of the Wacom tablet,
      as hidp does not support hid_output_raw_report.
      Signed-off-by: NBastien Nocera <hadess@hadess.net>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      ca2dcd40
  3. 30 3月, 2009 4 次提交
  4. 04 1月, 2009 4 次提交
  5. 15 10月, 2008 23 次提交
  6. 28 1月, 2008 1 次提交
    • J
      HID: refactor mapping to input subsystem for quirky devices · 10bd065f
      Jiri Kosina 提交于
      Currently, the handling of mapping between hid and input for devices
      that don't conform to HUT 1.12 specification is very messy -- no per-device
      handling, no blacklists, conditions on idVendor and idProduct placed
      all over the code.
      
      This patch moves all the device-specific input mapping to a separate
      file, and introduces a blacklist-style handling for non-standard
      device-specific mappings.
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      10bd065f
  7. 14 10月, 2007 1 次提交
    • J
      HID: add hidraw interface · 86166b7b
      Jiri Kosina 提交于
      hidraw is an interface that is going to obsolete hiddev one
      day.
      
      Many userland applications are using libusb instead of using
      kernel-provided hiddev interface. This is caused by various
      reasons - the HID parser in kernel doesn't handle all the
      HID hardware on the planet properly, some devices might require
      its own specific quirks/drivers, etc.
      
      hiddev interface tries to do its best to parse all the received
      reports properly, and presents only parsed usages into userspace.
      This is however often not enough, and that's the reason why
      many userland applications just don't use hiddev at all, and
      rather use libusb to read raw USB events and process them on
      their own.
      
      Another drawback of hiddev is that it is USB-specific.
      
      hidraw interface provides userspace readers with really raw HID
      reports, no matter what the low-level transport layer is (USB/BT),
      and gives the userland applications all the freedom to process
      the HID reports in a way they wish to.
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      86166b7b
  8. 11 4月, 2007 1 次提交
  9. 05 2月, 2007 2 次提交
  10. 09 12月, 2006 1 次提交