26 Feb, 2010

1 commit


10 Feb, 2010

2 commits

  • The Magic Mouse requires that a driver send an unlock Report(Feature) command,
    similar to the Wacom wireless tablet and Sixaxis controller quirks. This turns
    on an Input Report that isn't published in the input Report descriptor that
    contains touch data (and usually overrides the normal motion and click Report).

    Because the mouse has only one switch and no scroll wheel, the driver
    (under control of parameters) emulates a middle button and scroll wheel.
    User space could also ignore and/or re-synthesize those events based on
    the reported events.

    Some user-space tools to talk to the mouse directly (that is, when it is not
    associated with the host's HIDP stack) are at
    http://github.com/entrope/linux-magicmouse

    Signed-off-by: Michael Poole
    Signed-off-by: Jiri Kosina

    Michael Poole
     
  • Added support for MosArt dual-touch panels, present in the Asus T91MT notebook.

    Signed-off-by: Stephane Chatty
    Signed-off-by: Jiri Kosina

    Stephane Chatty
     

26 Jan, 2010

1 commit

  • This patch adds a new USB HID driver for the Ortek WKB-2000, working around an
    incorrect LogicalMaximum value in the USB resource descriptor.

    Tracked by http://bugzilla.kernel.org/show_bug.cgi?id=14787
    Bug originally reported by Ubuntu users: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/405390

    Signed-off-by: Johnathon Harris
    Tested-by: Daniel J Blueman
    Signed-off-by: Jiri Kosina

    Johnathon Harris
     

13 Jan, 2010

2 commits

  • Add support for the Quanta Optical Touch dual-touch panel, present in the Acer
    T230H monitor, HP L2105tm, and Packard-Bell Video 200t.

    Signed-off-by: Stephane Chatty
    Tested-by: Jerome Vidal
    Tested-by: Cedric Berthier
    Acked-by: Dmitry Torokhov
    Signed-off-by: Jiri Kosina

    Stephane Chatty
     
  • Implements a new USB-HID for Force Feedback based on the normal
    Logitech Force Feedback code and FF-Memless.

    Currently only supports the FF_CONSTANT effect although the joystick
    appears to support additional non-standard ones.

    Signed-off-by: Gary Stein
    Signed-off-by: Jiri Kosina

    Gary Stein
     

04 Jan, 2010

1 commit


23 Dec, 2009

1 commit


14 Sep, 2009

1 commit


23 Jul, 2009

1 commit

  • Add explicit key mappings for TwinHan USB HID remote control.

    All dummy Ctrl, Alt, Meta, ... key press/release events generated
    by the remote are silenced by "unmapping" them. This makes Power and
    Volume keys single-key and strips the regular (even while idle) key
    release events for Ctrl, Alt, Meta, ...

    Signed-off-by: Bruno Premont
    Signed-off-by: Jiri Kosina

    Bruno Premont
     

12 Jun, 2009

1 commit

  • It is a little bit inconvenient for people who have some non-standard
    HID hardware (usually violating the HID specification) to have to
    recompile kernel with CONFIG_HID_DEBUG to be able to see kernel's perspective
    of the HID report descriptor and observe the parsed events. Plus the messages
    are then mixed up inconveniently with the rest of the dmesg stuff.

    This patch implements /sys/kernel/debug/hid//rdesc file, which
    represents the kernel's view of report descriptor (both the raw report
    descriptor data and parsed contents).

    With all the device-specific debug data being available through debugfs, there
    is no need for keeping CONFIG_HID_DEBUG, as the 'debug' parameter to the
    hid module will now only output only driver-specific debugging options, which has
    absolutely minimal memory footprint, just a few error messages and one global
    flag (hid_debug).

    We use the current set of output formatting functions. The ones that need to be
    used both for one-shot rdesc seq_file and also for continuous flow of data
    (individual reports, as being sent by the device) distinguish according to the
    passed seq_file parameter, and if it is NULL, it still output to kernel ringbuffer,
    otherwise the corresponding seq_file is used for output.

    The format of the output is preserved.

    Signed-off-by: Jiri Kosina

    Jiri Kosina
     

15 May, 2009

2 commits

  • Currently, the hid-*ff force feedback drivers, which claim the blacklisted
    device on a HID bus, are only compiled in if the user selects force feedback
    support.

    However we want the device to be supported even when the kernel is configured
    without force feedback.

    This patch fixes the drivers in a way that they get compiled even if force
    feedback is turned off; all the force feedback support code is compiled out in
    such case, and the driver works as a usual driver on HID bus, claiming and
    initializing the device, making it operational without FF effects.

    Reported-by: Jussi Kivilinna
    Signed-off-by: Jiri Kosina

    Jiri Kosina
     
  • This driver adds force feedback support for SmartJoy PLUS PS2/USB adapter. I
    made this driver one device spesific instead of making generic 'wisegroup-ff'
    because I have another Wisegroup PS2/USB adapter that doesn't work same way as
    SmartJoy PLUS. If another device that is compatible pops up, this driver could
    be then renamed to something more generic.

    Signed-off-by: Jussi Kivilinna
    Signed-off-by: Jiri Kosina

    Jussi Kivilinna
     

13 May, 2009

1 commit

  • 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: Bastien Nocera
    Signed-off-by: Jiri Kosina

    Bastien Nocera
     

30 Mar, 2009

4 commits

  • This removal was scheduled and there is no problem with later
    distros to adapt for the new bus, thanks to aliases.

    module-init-tools map files are deprecated nowadays, so that
    the patch which introduced hid ones into the m-i-t won't be
    accepted and hence there is no reason for leaving compat stuff in.

    Signed-off-by: Jiri Slaby
    Cc: Jiri Kosina
    Signed-off-by: Jiri Kosina

    Jiri Slaby
     
  • This device sends several buttons in a separate field, which is
    wrongly described in the report descriptor. Fix it in the following
    way:

    - change led usage page to button
    - report size 8 count 1 becomes report size 1 count 8
    - the button usage range changed to 4-7 (the mouse has three buttons in
    a different field already).

    Reported-by: Tomas Hanak
    Signed-off-by: Jiri Kosina

    Jiri Kosina
     
  • 0x47d/0x2041 device sends two extra buttons in 0xff00 usage
    page and therefore requires special handling.

    Reported-by: Jason Noble
    Signed-off-by: Jiri Kosina

    Jiri Kosina
     
  • Adds force feedback support for USB DragonRise Inc. game controllers.
    These devices are mass produced in China and distributed under several vendors.

    Signed-off-by: Richard Walmsley
    Signed-off-by: Jiri Kosina

    Richard Walmsley
     

04 Jan, 2009

4 commits

  • I recently picked up a Cyberlink branded remote control produced
    by TopSeed Tech Corp. Alas, it appears that this device is using
    non-standard mappings for some of it's keys (Usage page 0xffbc).

    Signed-off-by: Lev Babiev
    Signed-off-by: Jiri Kosina

    Lev Babiev
     
  • I have implemented Force Feedback driver for another "GreeAsia" based device
    (0e8f:0012 "GreenAsia Inc. USB Joystick"). The functionality was tested with
    MANTA Warior MM816 and SpeedLink Strike2 SL-6635 and fftest software -
    everything seems to work right.

    Signed-off-by: Lukasz Lubojanski
    Signed-off-by: Jiri Kosina

    Lukasz Lubojanski
     
  • Added quirks for the N-Trig digitizer.

    Signed-off-by: Rafi Rubin
    Signed-off-by: Jiri Kosina

    Rafi Rubin
     
  • 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
    Signed-off-by: Alan Stern
    Signed-off-by: Jiri Kosina

    Alan Stern
     

15 Oct, 2008

18 commits