1. 23 11月, 2011 1 次提交
    • D
      HID: wiimote: Add extension support stub · cb99221b
      David Herrmann 提交于
      The wiimote supports several extensions. This adds a separate source file which
      handles all extensions and can be disabled at compile-time.
      
      The driver reacts on "plug"-events on the extension port and starts a worker
      which initializes or deinitializes the extensions.
      
      Currently, the initialization logic is not fully understood and we can only
      detect and enable all extensions when all extensions are deactivated. Therefore,
      we need to disable all extensions, then detect and activate them again to react
      on "plug"-events.
      However, deactivating extensions will generate a new "plug"-event and we will
      never leave that loop. Hence, we only support extensions if they are plugged
      before the wiimote is connected (or before the ext-input device is opened). In
      the future we may support full extension hotplug support, but
      reverse-engineering this may take a while.
      Signed-off-by: NDavid Herrmann <dh.herrmann@googlemail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      cb99221b
  2. 21 10月, 2011 1 次提交
  3. 17 10月, 2011 2 次提交
    • J
      HID: primax: remove spurious dependency · dfe9a312
      Jiri Kosina 提交于
      Remove Kconfig dependency for hid-primax driver on CONFIG_EXPERT.
      Please see changelog of 73d5e8f7 ("HID: fix up 'EMBEDDED' mess in
      Kconfig") for reasoning behind this.
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      dfe9a312
    • T
      HID: support primax keyboards violating USB HID spec · f6a04605
      Terry Lambert 提交于
      Primax keyboards with the issue this driver addresses report modifier
      keys as in band key events instead of as out of band modifier bits,
      resulting in the modifier keys generating key up events immediately
      before the keys they are intended to modify.  This driver rewrites
      the raw report data from such keyboards into USB HID 1.11 compliant
      report data.  It only matches the USB vendor and product IDs for the
      keyboard it has been tested on. Since there are several keyboards,
      notably a number of laptops and folding USB keyboards known to have
      similar unresolved problem reports, the list is expected to grow.
      Signed-off-by: NTerry Lambert <tlambert@chromium.org>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      f6a04605
  4. 15 9月, 2011 1 次提交
    • N
      HID: Add full support for Logitech Unifying receivers · 534a7b8e
      Nestor Lopez Casado 提交于
      With this driver, all the devices paired to a single Unifying
      receiver are exposed to user processes in separated /input/dev
      nodes.
      
      Keyboards with different layouts can be treated differently,
      Multiplayer games on single PC (like home theater PC) can
      differentiate input coming from different kbds paired to the
      same receiver.
      
      Up to now, when Logitech Unifying receivers are connected to a
      Linux based system, a single keyboard and a single mouse are
      presented to the HID Layer, even if the Unifying receiver can
      pair up to six compatible devices. The Unifying receiver by default
      multiplexes all incoming events (from multiple keyboards/mice)
      into these two.
      Signed-off-by: NNestor Lopez Casado <nlopezcasad@logitech.com>
      Signed-off-by: NBenjamin Tissoires <benjamin.tissoires@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      534a7b8e
  5. 07 9月, 2011 1 次提交
  6. 23 8月, 2011 1 次提交
  7. 16 8月, 2011 1 次提交
  8. 11 8月, 2011 1 次提交
  9. 04 8月, 2011 2 次提交
  10. 21 7月, 2011 1 次提交
  11. 11 7月, 2011 1 次提交
  12. 27 6月, 2011 1 次提交
  13. 13 6月, 2011 1 次提交
  14. 08 6月, 2011 1 次提交
    • S
      HID: Add driver to fix Speedlink VAD Cezanne support · 74bc6953
      Stefan Kriwanek 提交于
      Speedlink VAD Cezanne have a hardware bug that makes the cursor "jump" from one
      place to another every now and then. The issue are relative motion events
      erroneously reported by the device, each having a distance value of +256. This
      256 can in fact never occur due to real motion, therefore those events can
      safely be ignored.  The driver also drops useless EV_REL events with a value of
      0, that the device sends every time it sends an "real" EV_REL or EV_KEY event.
      Signed-off-by: NStefan Kriwanek <mail@stefankriwanek.de>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      74bc6953
  15. 07 6月, 2011 1 次提交
  16. 23 5月, 2011 1 次提交
  17. 20 5月, 2011 5 次提交
  18. 19 5月, 2011 1 次提交
  19. 18 5月, 2011 1 次提交
  20. 09 5月, 2011 1 次提交
  21. 22 4月, 2011 2 次提交
  22. 24 3月, 2011 1 次提交
  23. 22 3月, 2011 3 次提交
  24. 21 3月, 2011 1 次提交
    • J
      HID: add support for Skycable 0x3f07 wireless presenter · d586dca0
      Jiri Kosina 提交于
      This device contains the very same bug in report descriptor as the
      Ortek ones do (i.e. LogicalMinimum == 1, which is wrong for the key
      array).
      
      As we have more reports for the Ortek devices, we are keeping the driver
      name for now. Apparently there is a chip producer which sells chip with
      this buggy descriptor to multiple vendors. Thus if such reports start
      to come at highger frequency, we'll either have to rename the driver
      accordingly, or come up with more generic workaround.
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      d586dca0
  25. 17 3月, 2011 1 次提交
  26. 14 3月, 2011 1 次提交
  27. 13 3月, 2011 1 次提交
  28. 17 2月, 2011 1 次提交
  29. 03 2月, 2011 3 次提交