1. 04 Jan, 2009 1 commit
    • Alan Stern's avatar
      HID: automatically call usbhid_set_leds in usbhid driver · 08ef08ee
      Alan Stern authored
      This patch (as1146c) makes usbhid automatically call usbhid_set_leds()
      for any device that supports the keyboard boot protocol.
      
      In theory this should be perfectly safe.  BIOSes send the LED output
      report as part of their normal device initialization, so any keyboard
      device supporting the boot protocol has to be able to handle it.
      
      As a side effect, the hid-dell and hid-bright drivers are no longer
      needed, and the Logitech keyboard driver can be removed from hid-lg.
      
      CC: Mauro Carvalho Chehab <mchehab@redhat.com>
      Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      08ef08ee
  2. 14 Oct, 2008 23 commits
  3. 28 Jan, 2008 1 commit
    • Jiri Kosina's avatar
      HID: refactor mapping to input subsystem for quirky devices · 10bd065f
      Jiri Kosina authored
      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: default avatarJiri Kosina <jkosina@suse.cz>
      10bd065f
  4. 14 Oct, 2007 1 commit
    • Jiri Kosina's avatar
      HID: add hidraw interface · 86166b7b
      Jiri Kosina authored
      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: default avatarJiri Kosina <jkosina@suse.cz>
      86166b7b
  5. 11 Apr, 2007 1 commit
  6. 05 Feb, 2007 2 commits
  7. 08 Dec, 2006 1 commit