Skip to content
Snippets Groups Projects
  1. Jul 22, 2011
  2. Jul 21, 2011
  3. Jul 20, 2011
  4. Jul 14, 2011
  5. Jul 12, 2011
  6. Jul 11, 2011
  7. Jun 27, 2011
  8. Jun 24, 2011
  9. Jun 16, 2011
  10. Jun 14, 2011
  11. Jun 13, 2011
  12. Jun 12, 2011
    • Benjamin Tissoires's avatar
      HID: hid-multitouch: fix broken eGalax · b84bd27f
      Benjamin Tissoires authored
      
      Since the inclusion of eGalax devices in 2.6.39, I've got some
      bug reports for 480d and other devices.
      The problem lies in the reports descriptors: eGalax supports both
      pen and fingers, and so the reports descriptors contained both.
      But hid-multitouch relies on them to detect the last item in each
      field to send the multitouch events. In 480d, the last item is not
      Y as it should but Pressure. That means that the fields are not
      aligned and X,Y are at 0,0 (the other touch coordinates of the report).
      
      With this patch, the detection is made only when the field ContactID
      has been detected inside the collection.
      
      There is still a problem with the detections of the range as stylus
      and fingers may not have the same min/max, but it's a start.
      
      Signed-off-by: default avatarBenjamin Tissoires <benjamin.tissoires@enac.fr>
      Reviewed-by: default avatarHenrik Rydberg <rydberg@euromail.se>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      b84bd27f
  13. Jun 08, 2011
    • Stefan Kriwanek's avatar
      HID: Add driver to fix Speedlink VAD Cezanne support · 74bc6953
      Stefan Kriwanek authored
      
      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: default avatarStefan Kriwanek <mail@stefankriwanek.de>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      74bc6953
  14. Jun 07, 2011
    • Michael Bauer's avatar
      HID: Fix Logitech Driving Force Pro wheel · dc0a4f0c
      Michael Bauer authored
      
      - Add the quirk "NOGET" to make the wheel work at all in native mode.
      - Replace the somehow broken report descriptor with a custom one to have
        separate throttle and brake axes.
      
      As there are significant differences in the descriptor (original descriptor
      "hides" the separate axes in a  24 bit FF00 usagepage, new descripter replaces
      that with two individual 8 bit desktop.y and desktop.rz usages) I provided a
      complete replacement descriptor instead trying to patch the original one.
      Patching the descriptor seems not feasible as the new one is much larger.
      
      Note: To actually test this you have to use the tool "ltwheelconf" to put the
      DFP into it's native mode - See below for more info.
      
      Background:
      Most Logitech wheels are initially reporting themselves with a "fallback"
      deviceID (USB_DEVICE_ID_LOGITECH_WHEEL - 0xc294), in order to make sure they
      are working even without having the proper driver installed.
      
      If the Logitech driver is installed it sends a special command to the wheel
      which sets the wheel to "native mode", enabling enhance features like:
      - Clutch pedal
      - extended wheel rotation range (up to 900 degrees)
      - H-gate shifter
      - separate axis for throttle / brake
      - all buttons
      
      When the wheel is set to native mode it basically disconnects and reconnects
      with a different deviceID (USB_DEVICE_ID_LOGITECH_DFP_WHEEL - 0xc298 in this
      case).
      
      I am working on a userspace tool [1] which does the switching from fallback to
      native mode. During development I found out that the Driving Force Pro wheel
      is not supported in native mode - quierk NOGET is missing and the throttle and
      brake axes are reported in a combined way only.
      
      Signed-off-by: default avatarMichael Bauer <michael@m-bauer.org>
      Signed-off-by: default avatarSimon Wood <simon@mungewell.org>
      
      [1] https://github.com/TripleSpeeder/LTWheelConf
      
      
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      dc0a4f0c
    • Austin Zhang's avatar
      HID: hid-multitouch: add support for Chunghwa multi-touch panel · 942fd422
      Austin Zhang authored
      
      Added Chunghwa hid multitouch panel support into hid-multitouch.
      
      Signed-off-by: default avatarAustin Zhang <zhang.austin@gmail.com>
      Reviewed-by: default avatarBenjamin Tissoires <benjamin.tissoires@enac.fr>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      942fd422
    • Tomoki Sekiyama's avatar
      HID: yurex: recognize GeneralKeys wireless presenter as generic HID · 6dc1418e
      Tomoki Sekiyama authored
      Unfortunately, the device seems to have the same Vendor ID and Product ID
      as YUREX leg-shakes sensors, and the commit 6bc235a2 ("USB: add driver
      for Meywa-Denki & Kayac YUREX") added the ID to hid_ignore_list.
      
      I believe that we can distinguish YUREX and the Wireless Presenter by
      device type.  The patch below makes the driver ignore only YUREX
      (bInterfaceProtocol==0), and recognize Wireless Presenter
      (bInterfaceProtocol is keyboard or mouse) as generic HID.  (I don't have
      the Wireless Presenter, so not yet ested.)
      
      ** YUREX lsusb information:
      Bus 002 Device 007: ID 0c45:1010 Microdia
      Device Descriptor:
         bLength                18
         bDescriptorType         1
         bcdUSB               1.10
         bDeviceClass            0 (Defined at Interface level)
         bDeviceSubClass         0
         bDeviceProtocol         0
         bMaxPacketSize0         8
         idVendor           0x0c45 Microdia
         idProduct          0x1010
         bcdDevice            0.03
         iManufacturer           1 JESS
         iProduct                2 YUREX
         iSerial                 3 10000269
         bNumConfigurations      1
         Configuration Descriptor:
           bLength                 9
           bDescriptorType         2
           wTotalLength           34
           bNumInterfaces          1
           bConfigurationValue     1
           iConfiguration          0
           bmAttributes         0xa0
             (Bus Powered)
             Remote Wakeup
           MaxPower              100mA
           Interface Descriptor:
             bLength                 9
             bDescriptorType         4
             bInterfaceNumber        0
             bAlternateSetting       0
             bNumEndpoints           1
             bInterfaceClass         3 Human Interface Device
             bInterfaceSubClass      1 Boot Interface Subclass
             bInterfaceProtocol      0 None
             iInterface              0
               HID Device Descriptor:
                 bLength                 9
                 bDescriptorType        33
                 bcdHID               1.10
                 bCountryCode            0 Not supported
                 bNumDescriptors         1
                 bDescriptorType        34 Report
                 wDescriptorLength      31
                Report Descriptors:
                  ** UNAVAILABLE **
             Endpoint Descriptor:
               bLength                 7
               bDescriptorType         5
               bEndpointAddress     0x81  EP 1 IN
               bmAttributes            3
                 Transfer Type            Interrupt
                 Synch Type               None
                 Usage Type               Data
               wMaxPacketSize     0x0008  1x 8 bytes
               bInterval              10
      Device Status:     0x0002
         (Bus Powered)
         Remote Wakeup Enabled
      
      Addresses https://bugzilla.kernel.org/show_bug.cgi?id=26922
      
      
      
      Signed-off-by: default avatarTomoki Sekiyama <tomoki.sekiyama@gmail.com>
      Cc: Greg KH <gregkh@suse.de>
      Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
      Cc: Maciej Rutecki <maciej.rutecki@gmail.com>
      Reported-by: default avatarThomas B?chler <thomas@archlinux.org>
      Tested-by: default avatarThomas B?chler <thomas@archlinux.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      6dc1418e
  15. May 26, 2011
  16. May 24, 2011
    • Jimmy Hon's avatar
      HID: add quirk for HyperPen 10000U · e23be0a2
      Jimmy Hon authored
      
      Add 5543:0064 UC-Logic Technology Corp. Aiptek HyperPen 10000U to quirks with
      HID_QUIRK_MULTI_INPUT.
      
      Originally the device is reporting the x,y coordinates on Z and RX. By adding
      this quirk, there will be two kernel devices. The first one is muted and the
      second device will report coordinates on X and Y.
      
      Signed-off-by: default avatarJimmy Hon <honyuenkwun@gmail.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      e23be0a2
    • Jiri Kosina's avatar
      HID: hiddev: fix potential use-after-free · 7f77897e
      Jiri Kosina authored
      
      Commit 6cb4b040 ("HID: hiddev: fix race between hiddev_disconnect
      and hiddev_release") made it possible to access hiddev (for unlocking
      the existance mutex) once hiddev has been kfreed.
      
      Change the order so that this can not happen (always unlock the mutex first,
      it is needed only to protect access to ->exist and ->open).
      
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      7f77897e
Loading